Moofment is a community-driven companion app for VanMoof and Cowboy e-bike owners. Direct Bluetooth control of your bike, GPS ride tracking, turn-by-turn navigation with voice guidance, CityGuard geofenced speed zones, Moofify (peer-to-peer parts & bike listings), community events and Moofments, MoofMatch rider pairing, ferry and transit departures for 8 cities, the Hi feature for community greetings, music integration, and a scoring system, all in one app.
VanMoof: Series 1–2 (Electrified S, X, S2, X2), Series 3 (S3 & X3), Series 4 (S4 / Electrified S2), Series 5 (S5 & A5), and Series 6 (S6 & S6 Open), all with full Bluetooth control.
Cowboy: C1–C4 and Cross. Bluetooth connection, battery + speed + power telemetry, light toggle, auto-unlock / smart lock / crash detection / theft alert toggles, plus a legal speed-cap reset (25 km/h EU pedelec default). See the Cowboy section below.
English, German, French, Dutch, and Japanese.
VanMoof riders sign in with their VanMoof email and password. Cowboy riders sign in with their Cowboy account credentials.
No. A VanMoof or Cowboy account is required to sign in.
Go to Profile > Account > Log Out. This disconnects all active Bluetooth connections, syncs your score, and clears local data.
Yes, there’s a configurable keep-alive timer. When you close the control sheet, the connection stays alive for the duration you set. You can reconnect instantly when you reopen it.
Moofment automatically attempts to reconnect up to 3 times with increasing delays (2s, 4s, 6s). If all attempts fail, the connection state resets to disconnected.
Yes. Both Series 3 and Series 5 credentials can be exported for backup or use with other tools.
Depending on your bike model: lock/unlock, power assist levels, speed limit region, light mode (off/on/auto), bell sound, alarm mode, and sound volume. Series 3 also supports the full sound board with all factory sounds.
Speed region changes are for responsible use only. For example, riders in the US can use CityGuard to lower their speed limit to 25 km/h in selected areas, or use ASM in EU mode during slow traffic to save battery.
A fun feature for Series 3 bikes that lets you play all of your bike’s built-in sounds, bells, horns, alarms, system sounds, pairing tones, and even some hidden easter-egg noises.
Yes, on Series 3 / X3. Record a clip or pick an audio file, preview it before uploading, adjust the volume, and it replaces the stock bell. Swap the sound whenever you like.
A real-time GPS-based speed reading with smoothing filters for accuracy. It also shows your battery level, odometer, and current settings.
A large, readable dashboard designed for handlebar-mounted use. Shows real-time speed, battery, distance, and elevation in one view. Works across Series 1–6 plus Cowboy. Activates automatically above a speed threshold you set (default 10 km/h) or can be opened manually. During navigation it splits to show the map plus turn banner + stats; rotate your phone for a landscape variant with a wider panel.
Yes. Set your exact wheel diameter so speed, distance, and odometer readings stay accurate even if you've swapped to different tyres that change the effective diameter. Calibrate once, all downstream readings follow. Useful for S3/X3 where the ODO is firmware-computed from wheel revolutions.
C1, C2, C3, C4, C4ST, and Cross. Connection is over Bluetooth Low Energy using your Cowboy account credentials (for initial pairing) and locally stored BLE credentials afterwards.
A one-way action on the Cowboy control sheet that restores your bike's motor-assist cutoff to the EU pedelec legal default of 25 km/h. This is provided as a compliance aid for riders whose bike is currently operating above that cap. Moofment does not offer any option to raise the cap.
Warranty note: Any communication with your bike's firmware may theoretically affect your Cowboy warranty. Cowboy SA's warranty terms govern whether and how warranty is impacted. A disclaimer appears before you can use the feature.
No. Moofment is an independent third-party application. Cowboy is a registered trademark of Cowboy SA. Moofment is not affiliated with, endorsed by, or sponsored by Cowboy SA.
Locally on your device only. Your Cowboy email and password are used once for the initial API login to fetch your bike's BLE passkey, then discarded. The BLE passkey and MAC address are stored on-device and never transmitted to any Moofment server. See the Moofment CB Privacy Policy for details.
CityGuard is a geofence-based speed limit manager for responsible use. You define zones on the map (e.g., your city center or a busy area), assign a lower speed limit to each, and your bike’s speed limit automatically adjusts when you enter or leave a zone. Great for lowering your speed in pedestrian areas or saving battery in slow-traffic zones.
Open the CityGuard settings in the control sheet, create a zone by dropping a pin, set the radius (100 m to 20 km), and choose the speed limit for that zone. You can create up to 20 zones.
Yes. It uses background location updates to detect when you cross zone boundaries, even when the app is in the background. For optimal performance, keep your bike connected with the control sheet or FOCUS Dashboard open.
Adaptive Speed Mode automatically switches your VanMoof bike's regional setting based on your speed. When you pick up pace above a threshold, it shifts to the higher region; when you slow down or stop, it drops back. ASM is VanMoof-only; Cowboy bikes have no equivalent.
Note: You must keep the app connected to your bike with the control sheet or FOCUS Dashboard open for ASM to work.
The higher 32 km/h region may exceed the legal motor-assist cutoff for pedelec classification in your jurisdiction. The EU pedelec standard is 25 km/h (Directive 168/2013). Operating an e-bike that exceeds the legal cutoff on public roads may require insurance, registration, a helmet, and/or a driver's license, and may subject you to fines, impound, or prosecution. ASM is provided for use only on private property or where expressly permitted by local law. You are solely responsible for compliance.
ASM shows a mandatory disclaimer before activation. You must acknowledge what it does, that it may affect battery life and your warranty, that you are responsible for complying with local traffic laws, and that you should only use it on private property where applicable.
Amsterdam, Rotterdam, Hamburg, Berlin, Potsdam, Dresden, Konstanz, and the Stuttgart Zacke (a rack railway that carries bikes). Live departure times are fetched from the operator where available (Amsterdam GVB and Rotterdam Waterbus via OVapi); the other cities use the published schedule with a real-time countdown.
When you're within 10 km of a covered stop, a ferry or tram button appears on the Home dock. Tap it to open the departure board, which shows the next four services with route number, direction, and countdown. Live times are marked as such; estimates (schedule-based) are tagged EST.
Tap the ferry or Zacke pin on the map to open that stop's board, or open the Home dock card. Hit the blue Go button beneath the board; Moofment calculates a cycling route to the stop's coordinates and launches turn-by-turn.
Yes. Enable Departure alerts under Notifications → Events. You'll get a local notification about 2 minutes before the next departure at the stop you're closest to (within 1.5 km).
Live times come from the operator's own feed (OVapi for the Dutch networks), so they reflect real-time delays. Scheduled-only cities show the published timetable with a real-time countdown, if a service is delayed in reality, the countdown won't know. Always verify with the operator for critical journeys.
Pins: Preferences → Map → Bike-Friendly Transit Pins. Alerts: Notifications → Events → Transit Departure Alerts. Toggles are independent.
A daily community greeting. Tap Say Hi in the Hi card on the Home dock to send a wave to every other rider in your city today. It's visible as a live count, and the most recent waves show up with the city and the time.
City-level location only (not exact GPS), your bike name (shown only on your own wave so you can spot it in the list), and a timestamp. One Hi per rider per day, same daily cap for everyone.
An opt-in toggle inside the Hi card. When on, the first ride of the day triggers a Hi automatically when you tap Start Ride, saves you from having to remember. Respects the same once-per-day cap, uses the same city-level sharing, and only fires on manual ride starts (not motion-detected auto-starts).
Yes. Close the Hi card any time and it stops sending. The auto-greet toggle persists independently, you can leave Hi on and auto-greet off, or either combination.
Moofment connects to Apple Music & Spotify and shows what’s currently playing in a floating pill on the control sheet. You can play/pause and skip tracks directly from the pill.
When enabled, Moofment auto-queues songs that match your cycling speed based on BPM (beats per minute). Ride faster, get faster music.
The Now Playing pill works with Apple Music and Spotify.
Yes. There’s a toggle card on the control sheet to show or hide the music pill.
Moofment uses GPS to track your rides, distance, speed, duration, elevation gain, and calories burned. Rides are classified by intensity: recovery, easy, moderate, hard, or max effort.
Yes. When enabled, rides are saved as cycling workouts in HealthKit, including route data, distance, and calories.
A map view that overlays every route you've ridden, color-intensity weighted by how often you've ridden each segment. Useful for spotting your regular commute, discovering gaps in your exploration, and tracking how your riding footprint grows over time. Opens from the Map tab.
An estimate of how far you can ride and still make it home, drawn as two circles on the map, a one-way reach and a round-trip reach. The estimate adjusts for your bike's battery level, your typical ride style, terrain elevation, temperature, and wind when weather data is available. Enable under Preferences → Map → Range Circle.
An alternative map layer that color-codes your ridden routes by gradient steepness, green for flat, yellow for moderate, orange for steep, red for very steep. Helps you see which routes have been battery-draining climbs versus easy flats. Enable under Preferences → Map → Elevation Overlay.
A real-time widget that shows your speed, battery level, and ride stats on the Lock Screen and the Dynamic Island (iPhone 14 Pro and later). Starts automatically when you connect to a bike or enter FOCUS mode.
VanMoof S6 and Cowboy models. Other series don't expose the live telemetry needed to drive the activity.
Distance only updates while a ride is actually being recorded. Connecting to your bike starts the Live Activity (speed + battery), but the distance field stays at zero until you tap Start Ride in the FOCUS view, or until Ride Tracking's auto-start triggers.
iOS Settings → Moofment → Live Activities. Or inside the app: Preferences → Connection → Live Activities toggle, with a separate Ride Only toggle if you only want them during active rides.
MoofMatch connects VanMoof bikes in the area who want to ride together. Enter your preferences (when, how long, what type of ride), and Moofment matches you with compatible riders nearby.
The algorithm checks: same city, overlapping time slots, similar ride duration, and compatible riding category. When a match is found, a Moofment event is automatically created with a suggested meeting point.
Complete bikes and individual parts. Listings include photos, price, condition (Excellent/Good/Fair/Needs Repair), and location.
Go to the Moofify tab > List Bike. Fill in your bike details, set the price and condition, add photos, and publish. You earn 10 boost points for listing.
No. Moofment is a platform that connects listers and interested riders. All transactions, shipping, and payments happen between the two parties. Review the Moofify terms before listing.
Moofments are community events that bring bikes together. Organize a group ride, a meetup at a local spot, or a workshop, the idea is to get the bikes out and riding together.
Tap the “+” button on the main screen and select “Create Moofment.” Set the time, location, description, and publish. You earn 25 boost points for creating an event.
Bikes that frequently show up at specific locations earn “Mayor” status, a local recognition for being a regular presence in that area.
You earn Boost Points by using the app:
| Tier | Points |
|---|---|
| Kickstarter | 0 – 499 |
| Cruiser | 500 – 1,499 |
| Smart Rider | 1,500 – 2,999 |
| Booster | 3,000 – 5,999 |
| Legender | 6,000+ |
Card order is customizable (Analytics top bar → Reorder), and you can hide cards you don't use. On iPad, cards render in a two-column layout.
Yes. A small widget that shows your bike name, battery level, and odometer. It updates roughly every 15 minutes when iOS gives it a chance. Multiple bike sizes are supported.
Live Activities cover those surfaces, see the Live Activities section below.
Moofment can push your bike's state, battery level, lock status, speed mode, odometer, connection status, directly to your Home Assistant instance. Your bike becomes a device in your smart home, so you can automate lights, notifications, or dashboards around it.
Profile → Preferences → Home Assistant group. Enter your Home Assistant URL (local or Nabu Casa), tap Configure Token to paste a long-lived access token, and tap Test Connection. When the test passes, Moofment starts pushing state every time it has fresh data from the bike.
In the iOS Keychain, device-local. The token is never transmitted to any Moofment server, only to the Home Assistant URL you configured.
Only when you explicitly enable CityGuard (geofencing) or ride tracking. Location data stays on your phone unless you choose to share it.
Your data stays on your phone. Bike credentials are stored in the iOS Keychain. Only anonymous data is shared for Moofments, MoofMatch, and Moofify, and that data lives in Apple's secure iCloud infrastructure. No third-party servers are used.
A complete reference of VanMoof diagnostic error codes. These codes may appear on your bike's display or in the Moofment app diagnostics. Applies to Series 1–5.
| Code | Name | Description |
|---|---|---|
| 0 | BAT_SCP | Short circuit protection (main battery) |
| 1 | BAT_MOTP | MOSFET over temperature protection |
| 2 | BAT_PDSCP | Pre-discharge short circuit protection |
| 3 | BAT_PDOCP | Pre-discharge overload circuit protection |
| 4 | BAT_UVP2 | Under voltage protection 2, try charging longer |
| 5 | BAT_UVP1 | Under voltage protection 1 |
| 6 | BAT_OVP2 | Over voltage protection 2 |
| 7 | BAT_OVP1 | Over voltage protection 1 |
| 8 | BAT_COCP1 | Charge over current protection 1 |
| 9 | BAT_COCP2 | Charge over current protection 2 |
| 10 | BAT_DOCP2 | Discharge over current protection 2 |
| 11 | BAT_DOCP1 | Discharge over current protection 1 |
| 12 | BAT_CUTP | Charge under temperature, too cold to charge |
| 13 | BAT_COTP | Charge over temperature, too warm to charge |
| 14 | BAT_DUTP | Discharge under temperature, too cold to ride |
| 15 | BAT_DOTP | Discharge over temperature, too hot to ride |
| 16 | BAT_FP | Permanent fail (fuse burn), likely socket short circuit |
| 17 | BATTERY_NO_DSG | Could not set discharge mode |
| 18 | BATTERY_MISSING | Battery not recognized or absent |
| 19 | BATTERY_COMM | Battery communication error (Modbus) |
| 20 | BATTERY_NO_OUTPUT | BMS shutdown, sudden battery power loss |
| 21 | NO_CHARGE_CURRENT | Charging state but no current reported |
| Code | Name | Description |
|---|---|---|
| 22 | MOTOR_COMM | Motor chip communication error (SSP TI) |
| 23 | BLE_COMM | Bluetooth chip communication error (SSP BLE) |
| 24 | OAD_ABORT | Over-the-air update transfer aborted |
| 25 | OAD_CRC | OTA image CRC checksum error |
| 26 | OAD_TRANSFER | OTA file transfer took too long |
| 27 | OAD_PACK | No or invalid file in firmware pack |
| 28 | ICF_TIMEOUT | Timeout during flash programming |
| 29 | ICF_HEADER | Flash header not found |
| 30 | ICF_NO_FILES | No files in firmware pack |
| 31 | ICF_ERASE | Flash erase error |
| 32 | ICF_WRITE | Flash write error |
| 33 | ICF_CRC | File in pack has CRC error |
| 34 | PGM_MOTORWARE | Motor controller programming failed |
| 35 | PGM_BATTERYWARE | BMS controller programming failed |
| 36 | PGM_SHIFTERWARE | Shifter controller programming failed |
| 37 | PGM_BLEWARE | BLE controller programming failed |
| 38 | INTERNAL_BATTERY | Module battery read error, check battery module charging |
| 39 | READ_LIGHT_SENSOR | Light sensor I2C read error |
| Code | Name | Description |
|---|---|---|
| 40 | STUCK_HORN | Bell button pressed too long, possible water or short circuit |
| 41 | STUCK_BOOST | Boost button pressed too long, possible water or short circuit |
| 42 | KL_COIL_MISSING | Kick Lock coil not detected |
| 43 | SHIFTER_NOT_IN_GEAR | Gear not reached after 10 attempts |
| 44 | SHIFTER_COMM | E-shifter communication error, most common VanMoof error |
| Code | Name | Description |
|---|---|---|
| 45 | MOTOR_CABLE | Motor cable not connected / motor not recognized |
| 46 | MOTOR_OVER_CURRENT | Motor over temperature or over current detected |
| 48 | MOTOR_CONTROLLER | Motor controller error, may require motor replacement |
| 49 | MOTOR_CURRENT_ERR | Current offset calculation deviates from default |
| 50 | MOTOR_VOLTAGE_ERR | Voltage offset calculation error |
| 51 | MOTOR_DERATING | Max current limited due to high temperature |
| 52 | MOTOR_TORQUE_FAIL | Torque sensor failed |
| 53 | MOTOR_NOT_READY | Motor not ready during motor test |
| Code | Name | Description |
|---|---|---|
| 54 | NO_SIMCARD | SIM card not detected |
| 55 | I2C3_FAIL | I2C bus 3 communication error on startup |
| 56 | CCID_SIMCARD | SIM card has wrong CCID number |
| 57 | READ_SIMCARD | SIM card detected but no communication |
| 58 | GSM_MODEM | Modem startup sequence failed, often resolves after reset |
| Code | Name | Description |
|---|---|---|
| 60 | FACTORY_MODE | Factory firmware is loaded, bike needs production firmware |
First, try resetting your bike by holding the power button for 10 seconds. If the error persists, connect with Moofment to check diagnostics via Bluetooth. Many errors (especially 40, 44, 58) resolve after a reset. For battery errors (0–21), make sure your bike is charged and not in extreme temperatures. For motor errors (45–53), the bike may need physical service.
A known VanMoof Bluetooth communication error. If you see it, try: disconnect and reconnect, restart the bike, or restart the app.
Moofment uses a rolling median filter to smooth out erratic BLE battery readings. If the battery jumps more than 5% between readings, the spike is filtered out. Give it a few seconds to stabilize after connecting.
When first opening the control sheet, Moofment shows cached values from your last session (with a subtle pulse animation). Once the Bluetooth connection is established, fresh values replace the cached ones.
Make sure your bike is connected and authenticated. If you recently changed your encryption keys (e.g., reinstalled the app), you may need to re-register with the bike by connecting through the official VanMoof app first, then reconnecting via Moofment.
Mooflet is an alternative app for VanMoof S5 and A5 e-bikes. It connects to your bike via Bluetooth and lets you control settings, track rides, and monitor battery, all without the official VanMoof app. Available on both iOS and Android.
When connected, the home screen shows a large speedometer displaying your current GPS speed in km/h. The speed text turns red if you exceed your set speed limit.
Below the speed you’ll see:
Tap the lock control to lock or unlock your bike. If the bike is locked, tapping immediately unlocks it. If unlocked, a picker appears to choose between locked and unlocked states. Haptic feedback confirms the action.
Controls the motor assist level. Choose from Off, Level 1, Level 2, Level 3, or Level 4. Higher levels give more motor assistance but use more battery.
Set the bike’s lights to Off, On, or Auto. Auto mode uses the bike’s built-in light sensor to turn lights on and off automatically.
Choose between four bell sounds: Ding Dong, Party Horn, Ping, and Sonar. The bell is triggered by the physical button on your bike.
VanMoof S5/A5 bikes have region-based speed limits that determine the maximum speed the motor will assist you:
| Region | Speed Limit |
|---|---|
| EU | 25 km/h |
| USA | 32 km/h |
| Japan | 24 km/h |
Mooflet lets you switch between these regions from the speed limit picker on the home screen.
See the Certificate & Authentication section below. Speed limit changes require your app to hold the primary certificate on the bike.
Adaptive Speed Mode automatically adjusts your bike’s speed limit based on how fast you’re riding, using your phone’s GPS. Instead of being locked to one speed limit, the bike dynamically switches between EU (25 km/h) and USA (32 km/h) limits depending on your current speed.
ASM monitors your GPS speed in real time and uses two thresholds with hysteresis to prevent rapid switching:
The hysteresis gap (9 to 22 km/h) means the bike won’t constantly switch back and forth when you’re riding near a threshold. Changes are also debounced by 300 ms to prevent rapid fluctuations.
Moofment offers more granular ASM options compared to Mooflet.
Open the speed limit picker on the home screen and select “Adaptive Speed Mode.” The first time you enable it, a disclaimer screen explains how ASM works and asks you to acknowledge:
Tap “I Understand, Enable ASM” to confirm.
ASM works by sending regional setting commands to the bike based on your GPS speed. Under the hood, it’s calling the same command as manually changing the speed limit. If your app’s certificate is secondary, the bike silently ignores these commands and the speed limit never actually changes, even though the app shows ASM as enabled.
Mooflet automatically tracks your rides using GPS when connected to your bike:
During a ride, the dashboard shows real-time statistics:
Mooflet uses high-accuracy GPS positioning and applies several filters:
A ride is only saved if it meets both:
Short movements (walking to a store, repositioning the bike) are automatically filtered out.
When enabled, a compact now playing card appears at the bottom of the home screen showing:
You can also swipe the card left to skip forward or right to go back.
Go to Settings and toggle on “Music Player.”
The now playing card only appears when:
When enabled in Settings, Mooflet automatically saves completed rides as cycling workouts to Apple Health. Each workout includes:
Your health data stays on your device and is never uploaded anywhere.
Mooflet integrates with Google Health Connect to save cycling workouts. Each workout includes:
To set up, go to Settings and tap “Google Health Connect” to grant the necessary permissions. Google Health Connect must be installed on your device.
Mooflet uses Bluetooth Low Energy (BLE) to communicate with your VanMoof S5 or A5. When you log in with your VanMoof account, the app retrieves your bike’s encryption keys from VanMoof’s servers and uses them to authenticate over Bluetooth.
When enabled in Settings, Mooflet automatically connects to your last-used bike when you open the app. Disable this if you prefer to connect manually.
Yes. If your VanMoof account has multiple bikes, you can switch between them in Settings. Tap your bike name to see all available bikes and select a different one. The app will disconnect from the current bike and connect to the new one.
Yes. While connected to your bike, Mooflet prevents the screen from turning off so you can always see your speed and controls while riding. The screen lock returns to normal when you disconnect.
Choose between Dark, Light, or System appearance. System mode follows your device’s current dark/light mode setting.
When enabled, you’ll feel a subtle vibration when locking/unlocking and changing settings. Disable this if you prefer no haptic response.
In Settings under Debug, you can clear cached Bluetooth certificates. This forces the app to re-negotiate authentication with the bike on the next connection. Use this if you’re experiencing persistent connection issues.
Signs out of your VanMoof account, clears all local data (credentials, bike info, preferences), disconnects from the bike, and returns to the login screen.
The bike uses certificate-based authentication. Each app generates a key pair, sends the public key to VanMoof’s API, and receives a signed certificate back. This certificate is then presented to the bike during BLE connection. The bike verifies the certificate signature and grants access.
The bike treats regional settings as a privileged command. Only the primary certificate, the first certificate ever registered on the bike, has permission to change regional settings. Any subsequent certificates from other apps are treated as secondary and can lock/unlock, read state, change lights, bell, power level, etc., but cannot change regional settings. The bike silently ignores the command with no error response.
There is no BLE command to query certificate privilege level. The only indicator is behavioral: if set regional setting commands produce no topic response from the bike, your certificate is secondary. Primary certificates get an immediate topic update confirming the change.
Yes. If both apps are signed by the same Apple Developer Team, they can share it. Mooflet and Moofment share it, therefore you can use them both if you like.
Whichever app runs first generates the key. The other finds and reuses it. Same key = same certificate = same bike permissions.
Not easily. Android’s KeyStore is sandboxed per app. In practice, if only one Android app talks to the bike, it naturally becomes the primary certificate holder.
Not directly. The bike doesn’t care about platform, it cares about the certificate. If someone uses Moofment on iOS and Mooflet on Android on the same bike, they have two different certificates, and only the first-registered one gets regional settings privileges. Solving this requires syncing the private key across platforms (export, cloud sync), which has security implications.
Options:
The exact limit is unknown, but the bike accepts multiple certificates. Each certificate gets independent authentication but different privilege levels.
Try clearing certificates in Settings > Debug > Clear Certificates, then reconnect. This forces a fresh authentication and topic subscription.
Your certificate is likely secondary. See “Why can’t my app change regional settings?” above for details and solutions.
Same as above. ASM requires the primary certificate to send regional setting commands. If your certificate is secondary, the bike silently ignores all speed limit changes from ASM.
On Android, Mooflet runs a foreground service for GPS tracking while connected. This shows a persistent notification (“Mooflet – Tracking your ride”) and is required by Android to access GPS in the background. The notification cannot be removed while tracking is active.
Mooflet stores all data locally on your device:
Mooflet is an independent third-party app. VanMoof is a trademark of VanMoof B.V. Mooflet is not affiliated with, endorsed by, or connected to VanMoof or its parent company.