Berlin Cycling

TL;DR
  • RSVP on meetup.com/berlin-cycling — it's the only thing that counts
  • Keep your RSVP current. Change it at least 24 hours before
  • Don't show up without a confirmed spot
  • Come prepared: roadworthy bike, right clothes, enough water
  • Safety first: if something feels off, tell the organiser

Every event you see here was planned, scouted, and led by someone giving up their own time and money to make sure you have a great day out — and it's completely free for you to join. No strings attached. The least you can give back is being nice. Bringing homemade cake is not required, but it would make you an instant legend. We're a volunteer-run community that loves being on two wheels and welcomes anyone who wants to create and share memorable moments with others. To keep things running smoothly, we have a handful of ground rules that have proven both necessary and surprisingly helpful. They mostly boil down to: be considerate, show up when you say you will, and don't be that person.

  1. Keen to join an event? Brilliant — just RSVP on the event page on Meetup. It's the single source of truth. Everything else is just a rumour.
  2. If you can't make it, cancel at least 24 hours before. Your spot is someone else's Sunday plans. Repeated no-shows may get you removed from the group.
  3. On the waiting list? Wait. Turning up anyway without a confirmed spot — that's gate-crashing, and it gets you removed immediately. No exceptions, no hard feelings, just logic.
  4. No-shows and gate-crashing are both considered pretty bad form — and a genuine slap in the face to the person who spent their weekend planning the whole thing. Don't be that person. We mentioned that already. We meant it.
  5. Got removed for too many no-shows? Host at least one event and you're welcome back.
  6. Be decent to each other. Harassment or discrimination gets you removed. Full stop.
  7. Don't post photos of people without asking first. Not everyone wants their windswept face on the internet.
  8. Leave no trace. The road and the forest were here before us.
  9. And if none of the above covers your specific situation — common sense is your friend. It's free, always available, and works surprisingly well on a bike.

TL;DR

TL;DR
  • Got a good route? Make friends by leading it — anyone can host
  • Be clear: share the distance, pace, terrain, and what bike is needed
  • On the day: count heads, brief the group, ask about fitness and bike condition
  • Keep it free: events are always free — actual costs like train tickets, split them fairly
  • Keep it safe: always have a plan B — and check if bikes fit on that train
  • Keep it fair: update the attendance list afterwards to note any no-shows

Anyone can host a ride — and we'd genuinely love it if you did. Know a good route? Want to share it with a bunch of enthusiastic cyclists who will thank you, follow you, and occasionally complain about the hill you definitely mentioned but they somehow missed? You're already qualified. Get in touch with the head organiser via the form on the front page to get access.

When you post your event, be honest and thorough — distance, pace, terrain, what bikes work, what to bring. The more people know upfront, the fewer "nobody told me it was gravel" moments on the road. And trust us, those moments are memorable for all the wrong reasons.

On the day, count heads before you leave and keep counting. Give a quick briefing at the start: where you're going, roughly how long it'll take, and what to do if something goes wrong. Ask about fitness levels and bike condition before you set off — not when someone's already struggling five kilometres in.

A few things every organiser should know:

  1. Berlin Cycling events are free. No ticket fees, no ads for other groups, no donation drives. If the route involves real costs — transport, entry fees, that sort of thing — note them clearly in the event and split them fairly. Just honest cost-sharing between people who wanted a good ride.
  2. Don't plan routes people can't safely bail out of. If someone needs to stop, they need to actually be able to stop. Check if bikes are allowed on the return train — and have a plan if they're not.
  3. Mark no-shows on the attendee list afterwards. It takes two minutes and keeps things fair for everyone on the waiting list who actually wanted to come.

Interested in hosting? , make it yours, and reach out. The only thing worse than a bad ride is a good route nobody knows about.

TL;DR
  • Berlin Cycling is run entirely by volunteers — no company, no salary, no safety net
  • You're responsible for your own safety and the condition of your bike
  • By signing up you accept the risks that come with outdoor cycling
  • We reserve the right to remove anyone who repeatedly breaks the rules

Berlin Cycling is run entirely by volunteers. No company backs us, nobody gets paid, and the head organiser funds the whole thing out of their own pocket. This group exists purely because people love being on two wheels together — and we'd like to keep it that way.

The boring-but-important bit: by signing up for an event, you acknowledge that outdoor cycling involves real risks — traffic, uneven surfaces, unpredictable weather, mechanical failures, and the occasional confused pedestrian. You take personal responsibility for your own safety and that of anyone you bring along, and agree not to hold the event organiser liable for anything that goes wrong. They planned the route, not the weather — nor the pothole. They're volunteers, not insurance policies.

Make sure your bike is roadworthy before every ride. Brakes, tyres, lights, chain — your responsibility, not ours.

Berlin Cycling reserves the right to remove anyone who repeatedly breaks the rules, puts others at risk, or makes this a less welcoming place. We've rarely had to use that right. Let's keep it that way.

Event Template
========== FACTS ==========
ROUTE: [Start] > [Waypoint] > [End]
LEVEL: [Easy-Peasy / Intermediate / Advanced]
DISTANCE: [X] km
MEETING POINT: [HH:MM] - [Station / Location]
REQUIREMENTS: [The most important things to bring or be aware of]
========== FACTS ==========

========= DETAILS =========
ROUTE:
[Describe the route in a way that makes people want to come. Mention highlights — a café, a viewpoint, a canal path, a bridge with a good story. If there's something worth stopping for, say so. If there isn't, the ride will speak for itself.]

SPEED:
[Describe the pace in human terms, not just km/h. "Fast enough to feel the wind, slow enough to have a conversation" works better than "20 km/h".]

DISTANCE AND TERRAIN:
[What kind of ground will people be on? Cycle paths, gravel, cobblestones, forest tracks? What bikes work, what don't? If someone shows up on a road bike or a rental and struggles, they were warned.]

REQUIREMENTS:
[What does someone need to show up with? A roadworthy bike, helmet, lights, tools, spare inner tube. Be direct — if a fixie or rental bike won't cut it, say so clearly. Nobody enjoys finding out three kilometres in.]

MEETING POINT:
[Be specific. Not just the station — which exit, which end of the platform, which landmark. Bonus points for "I'll be the one with the [colour] bike looking mildly anxious".]

TICKET:
[What tickets do people need for the train? Give prices if you know them. Don't forget the bicycle day ticket — nobody likes a surprise at the machine.]

WAY OUT:
[HH:MM] - dep. [Station], platform [X], [train] towards [Destination]
[HH:MM] - change at [Station], arr. platform [X], switch to platform [X], [train] towards [Destination]
[HH:MM] - arr. [Final Station]

WAY BACK:
[HH:MM] - dep. [Station], platform [X], [train] towards [Destination]
[HH:MM] - change at [Station], arr. platform [X], switch to platform [X], [train] towards [Destination]
[HH:MM] - arr. [Final Station]

[Always check the schedule on the morning of the event — DB has a talent for last-minute surprises. And while getting there is exciting, getting back is where plans go to die — make sure yours doesn't. Can bikes actually get on that train? What happens if it's full, cancelled, or simply decides not to exist? Have a plan B. Write it down. Share it. Your group will thank you.]

RECOMMENDATIONS:
[Anything people should know, check, bring, or prepare. DB schedule changes, tyre pressure, chain oil, snacks, water, a spare inner tube and a basic tool kit. The stuff that sounds obvious until someone doesn't do it.]
========= DETAILS =========