ZuMoBi – カーシェアリングと公共交通機関のためのモビリティプラットフォーム

Start with a single, intelligent platform to rent a car or plan transit, a central hub that enables seamless options and real-time time and traffic updates, so users act quickly and confidently.

We deliver large datasets that reveal how much time you save and how emissions improve when fleets align with demand. The new pricing model supports rentals and passes like the Deutschlandticket, with rates that can adapt by the hour and by location, and the app ensures passes are ready when you need them, well integrated with transit timetables. In addition, this setup lets a user activate a Deutschlandticket within minutes.

For riders, ZuMoBi unifies car sharing and public transit, allowing our users to compare door-to-door options across all modes, with real-time guidance. The platform highlights benefits like faster trips, lower costs, and access to the Deutschlandticket, and it supports numerous routes in the city.

To launch efficiently, run phased pilots in dense urban areas, gather feedback, and scale through our API integrations with fleets. Track metrics like on-time share, vehicle utilization, user satisfaction, and costs saved. Also, provide simple onboarding for operators and keep the interface well accessible to all, reducing idle time during peak hours and improving traffic flow.

How ZuMoBi aligns car sharing with FlixBus schedules for multi-modal trips

Recommendation: keep a duration buffer of 25–30 minutes between car pickup and FlixBus departure to guarantee on-time boarding, making the transfer clean and safe for all travelers. Use reserved zones near the bus terminal to simplify handoffs and reduce last-mile friction, and track each car in real time to avoid taking the wrong vehicle.

ZuMoBi aligns car sharing with FlixBus schedules by pulling live timetables and car availability, then generating a combination of recommended options where the bus leg and the car leg meet the needs of all travelers. The system varies by city and hour, and it highlights partners and services that participate in the multi-modal flow, so users see a clear role for each step towards their destination. This approach keeps the experience sustainable and much more predictable for urban mobility in Berlin and beyond.

Implementation starts with mapping where FlixBus hubs sit and where car-sharing stations are clustered, especially near major terminals. Define an additional, reserved pickup zone at each hub so riders don’t wander between stops, and set a standard time window that ZuMoBi users can rely on. It is important to keep the experience sustainable (very much) by prioritizing electric or low-emission fleets from company partners, and to publish all pricing in euros so riders understand the total cost before booking. In Berlin, this creates a consistent workflow for partners, and everyone, with a simple role that guides users from car pickup towards the bus platform without confusion.

Start by creating your ZuMoBi account in minutes: tap Sign Up, enter a valid email, set a strong password, and confirm your mailbox. On the central dashboard, set your goal of easy cross-transport bookings, and let ZuMoBi’s system guide you through a quick, digital onboarding.

From Settings > Integrations, click Link FlixBus and authorize access. Once connected, ZuMoBi pulls FlixBus buses data, seat maps, and price points. The linkage includes discounts for students and a pass option for frequent travelers, included.

Configure defaults: language, currency, and billing contact. Save passenger profiles to speed up future bookings. Review rules for changes and refunds; if you encounter any problem, the blog always provides practical steps. We have a clear work rhythm and a straightforward setup, with guidance for possible issues.

Search and switch routes quickly: after selecting a date, ZuMoBi presents FlixBus options; you can switch to another date or change to a short trip with a single click. The central flow keeps all tickets in one place, ready for email or mobile pass, and avoids unnecessary delays.

Practical tips: flag your status as a student to unlock discounts; traveling with dogs? Check FlixBus pet policy and mark the animal in ZuMoBi. Switch to Spanish or German for bilingual support; our customer support team helps with questions. Due to regional rules, always verify ID and pass requirements before booking. For work trips, use a pass to save on multiple journeys. For updates, read the blog; this guidance helps Spanish speakers navigating cross-border routes. If you experience any issue, contact support.

Creating end-to-end itineraries: integrating live car availability with bus timetables

Start by synchronizing live car availability from montransportcom with bus timetables to create end-to-end itineraries in ZuMoBi. Build on our own data model to map pickup points, drop-offs, and central hubs, and to connect S-Bahn lines when relevant. This approach lets users see a single path that combines a car leg with a transit leg, reducing waiting times and simplifying planning.

Ingest car statuses (available, reserved, in use) and real-time bus schedules, normalize times, and resolve changes. Store results in the data model and expose an API to generate itineraries on demand. Include sending notifications and clear escalation paths if a service alteration affects a plan, so users stay informed and can pay for a multi-modal trip without surprises.

Offer itineraries that include walking segments from central hubs to pickup points, with transfer times clearly labeled. Provide a single, transparent price that includes all legs so users know what they pay upfront, and allow canceling the car leg if a user prefers a pure transit option. For partners, enable data sharing and a streamlined payment model that matches their preferred method and monthly billing cycle.

Example: for a region around a major center, users see several options that combine S-Bahn with car sharing at points near shopping areas. The flow emphasizes speed and predictability, and it definitely showcases how the two modes complement each other within regions that demand flexible mobility. If a ride is reserved, the system prompts an alternative route and sends a revised plan, keeping the user informed and engaged.

Schedule changes or availability issues become a ‘problem’ only if not surfaced promptly; the solution flags possible infractions and automatically recalculates the sequence. The experience remains user-centric, and Mari and others will see that the route adapts as needed. If a user prefers, they can switch to a fully connected plan and be notified about any adjustments; the solution supports monthly plan tiers for ongoing access.

Data sources and matching logic

Fuse live car data from montransportcom with transit timetables from regional networks, align on a common timeline, and compute optimal transfer points. Use region-aware heuristics to balance walking time with waiting time, prioritizing central hubs and S-Bahn connections. The matching logic accounts for reserved statuses and ensures that changes trigger a fast re-optimization, so users stay on track.

User experience and monetization

Present a concise, actionable itinerary with a single call to action to confirm the plan. Include a clear pay button and a seamless cancel flow if the user needs to adjust the plan. Offer various options across regions, enabling users to compare routes quickly. For monthly billed users, provide feature previews and periodic update notifications that keep the experience fresh and reliable. The result is a robust, user-friendly flow that definitely enhances multi-modal travel with ZuMoBi.

Routing preferences in ZuMoBi: time, cost, and sustainability prioritized

Recommendation: Set Time-first routing as the default in ZuMoBi, then layer Cost and Sustainability filters to surface the best balance. Before you start, consult the live options and verify that the available mode matches your schedule; check the same route for consistency. The system shows points and coverage across the city, including nighttime services, and we have real-time data to support decisions. The user-friendly interface supports international users, with German prompts to assist German travelers; monthly updates add new bus and S-Bahn options, so review the plan and, if helpful, buy tickets in advance for premium routes that save time.

Time-first routing during peak hours

During peak hours, Time-first routing prioritizes high-frequency S-Bahn and bus corridors with strong on-time performance. There are green corridors that reduce emissions by up to 30% compared to car trips, while keeping total travel time within a 10–15% margin of the fastest option. For families with children, choose routes with fewer transfers and accessible stops at major points; nighttime services are listed with ETA estimates to help you plan. If you want quicker certainty, consider premium routes that guarantee tighter ETAs and easier transitions.

Cost, sustainability, and premium options

Cost and sustainability balance: compare the base route with premium options; premium routes often carry a small premium but can cut travel time and emissions. There are passes designed for monthly use, and you can review fare and CO2 scores before you buy tickets. Use filters to lock a plan that respects your budget and environmental goals; due to traffic variability, the system may propose nighttime alternatives. We have resources for international users, with German labels to help German travelers. Continued.

Managing payments and tickets: single checkout for car shares and FlixBus rides

Implement a unified checkout that covers car-share payments and FlixBus tickets in one digital receipt. This helps users by reducing steps, eliminating complications at checkout, and making reviewing purchases simple. For companies, this approach delivers superior cash flow, faster settlement, and a consistent booking experience; because the user sees one cost, one payment method, and one ticket, conversion rises.

• Single payment token that covers both car shares and FlixBus rides, with one receipt and ticket ID
• Transparent cost breakdown showing cost, taxes, and any premium charges before purchase
• Support for multiple payment methods (cards, wallets, direct debit) and an optional premium tier for high-value trips
• Immediate e-tickets and digital receipts, ready to review in the app and downloadable for each trip
• Compliance with regulations and data privacy; PCI-DSS and GDPR alignment, with clear consent and data minimization
• Fraud protection and risk-based verification to minimize complications during purchases
• Integrated help access within the flow so users can review purchases without leaving the interface

Operational impact and outcomes: this single checkout reduces average checkout time from about 90 seconds to 55–65 seconds, decreases cart abandonments by 15–25%, and increases completed trips by 8–14%. It also optimizes cost by consolidating processing across mobility partners, allowing savings in interchange fees and better negotiation with companies; the result is a smoother experience for the user, and less support required for disputes.

実用的な実装とユーザーエクスペリエンス

Define scope: include car shares and FlixBus rides, plus optional train connections when available, as part of this flow
トークン化、クロスプロダクト決済、および統一された領収書を備えた単一の支払ゲートウェイを選択してください
Design a clean checkout UI: one cart, one total, one receipt, and a clear line for each trip
チケット発行ルールの設定：自動チケット発行、車両アクセスおよびバス乗車のための有効な検証
Security and compliance: regulations adherence, data retention controls, and user consent captured upfront
Testing and rollout: pilot with 2–3 companies in a mix of urban and long-distance routes; monitor reviews and feedback

チケットオプションとユーザーの選択

Offer standard and premium options; let the user select their chosen tier to access extras such as flexible changes or priority boarding
Support varied trips within a single itinerary, including multi-leg routes and dispatch costs across modes
Include train and bus alternatives where feasible to maximize options without complications

データプライバシーとセキュリティ：コネクテッドモビリティプラットフォームにおけるライダー情報の保護

Adopt a privacy-by-design baseline: enable default encryption for rider data in transit and at rest, enforce data minimization, and apply least-privilege access across all services. Encrypt data in transit with TLS 1.3 and at rest with AES-256; rotate keys every 90 days and require MFA for all staff with access to rider information. Map data flows across montransportcom and internal services to enforce strict boundaries between ride data, billing data, and home data. Tokenize and mask location data, keep sensitive fields separate, and anonymize analytics to protect individuals’ status. Retain data only as long as necessary to support services and legal obligations; define a data retention period that complies with regulations for urban mobility and with German privacy standards where applicable. Respond to data access or deletion requests within minutes, and maintain an immutable audit trail of all data accesses. Ensure collection reflects needs and that you have clear notices on how data is used, with user-friendly options to opt out of non-essential processing. Support a transparent ticket and receipt flow, enable confident trip planning, and clearly communicate how discounts and transport data translate to euros and the overall cost to the company that provides buses and car sharing, creating a reliable experience for people at home and on the move.

技術的な制御とデータ処理の実践

Enforce role-based access controls and least-privilege permissions across all teams. Keep data segmentation tight so a breached component cannot expose data across modules; apply pseudonymization for analytics and frequent token rotation to reduce re-identification risks. Use automated monitoring for anomalous access attempts and integrate security alerts into everyday workflows so responders can act in minutes rather than hours. Maintain secure APIs with strict input validation, rate limiting, and mutual TLS between services, including connections to montransportcom. Require secure coding practices, regular vulnerability management, and quarterly penetration tests to catch new vectors before they affect users who rely on urban mobility services. Build a user interface that makes privacy settings clear and comfortable to adjust, so riders can manage permissions without sacrificing speed or convenience.

ガバナンス、ライダーの権利、インシデント対応

Define a clear data retention and deletion policy aligned with regulations and regulatory expectations; publish stateful records of retention decisions and ensure data erasure completes within minutes after a valid request. Establish a formal process for rider data access requests and corrections, with verifiable identity checks and documentation of the status of each request. Maintain a data breach response plan that includes immediate containment steps, customer notifications, and a post-incident review to identify changes needed in processes or technology. Regularly train the team on privacy principles, including how to ensure minimum data sharing with third parties and how to handle payments, tickets, and receipts without exposing sensitive data. Ensure that the company behind the platform respects individual rights, offering clear explanations about how data such as transport patterns, trips, and preferences are used to improve services, while keeping home and travel location data protected.