Skip to content

00 / Software · Rail operations

Software for rail operators, from the developers of Bremshelfer.

We build software for rail operators (Eisenbahnverkehrsunternehmen, EVU) where your dispatch system stops: apps for the cab, forms instead of paper, APIs between your systems. Our app Bremshelfer calculates brake percentage (Bremshundertstel) for train drivers under Ril 915, even without a signal.

Intro call €0We usually reply the same business day

01 / Already built

What we’ve already built for train drivers.

Bremshelfer is our own product, not a client job. The app calculates a train’s brake percentage under Ril 915 and shows every deduction below the result. We built it together with a train driver.

  • 01

    Every rule visible

    Below the result it says which deduction applied for the train length, which brake position and which warning. Anyone who wants to check the math can.

    Calculator in the browser ↗
  • 02

    Multiple locomotives too

    Each locomotive gets its own deduction, and the app recommends the brake position. Six classes from BR 182 to BR 193 are preloaded, you can add more yourself.

  • 03

    Everything on the device

    Calculation, locomotive classes, history and formula reference are stored on the phone. The screenshots on our product page were taken in airplane mode.

  • 04

    Feedback from the app

    Train drivers send us their feedback directly from the app. Nobody has to look up an address to report something.

    View case study ↗

02 / In rail operations

What’s different in rail operations.

An app in the cab works under different conditions than a program in the office. We built these four into Bremshelfer, and they apply to everything we build for rail operators.

  • 01

    Out on the line there’s often no signal

    In tunnels, in cuttings, in the countryside. So whatever the driver needs on the way is stored on the device. Bremshelfer even collects its usage statistics there and only sends them once there’s a signal again.

  • 02

    The rulebook decides

    What applies is set out in Ril 915 and in your company’s own rules. So our software shows which rule it calculates by, and it takes your rules. In Bremshelfer you enter your own deductions by hand.

  • 03

    Shift work

    Calculations happen at four in the morning too, when there’s nobody around to ask. The interface has to explain itself: enter the train, choose the class, calculate.

  • 04

    Traceable, later too

    Earlier calculations stay in the history on the device, with result and locomotive class. If someone asks later what you calculated with, you look it up there.

03 / For rail operators

What we build for rail operators.

This is what we offer, not a list of references. Apart from Bremshelfer, we haven’t built anything for rail operations yet. Projects from other industries show how we build the individual parts.

  • 01

    Specialist apps for train drivers

    An app that calculates or checks a rule from your rulebook, on the device and without a signal. With the working shown below the result, like in Bremshelfer.

  • 02

    Forms instead of paper

    Reports, checklists, handovers: filled in on the phone, even in a dead zone, and sent as soon as there’s a signal again. They arrive in the office complete and legible.

  • 03

    APIs to your dispatch system

    Data moves from one system to the next without anyone typing it in again. At Turkish Home, the prices in the shop come from the retailer’s POS system every morning.

    View Turkish Home ↗
  • 04

    Portals for the office

    The list on the shared drive becomes a system in the browser, with roles, login and audit log. That’s how Zularis is built, our CRM for vehicle registration services. It has been running at a registration service in Duisburg since May 2026.

    View Zularis ↗

04 / Next to your dispatch

Next to your dispatch system, not in its place.

For dispatching, rostering and train preparation there are ready-made systems, such as zedas®cargo or dispoboxx. We don’t rebuild those.

We build what’s missing next to them. If it can be bought off the shelf, we tell you in the intro call.

Stays
Dispatching, rostering and train preparation in your system
Gets added
The form that runs on paper today. The list someone keeps in Excel. The tool for out on the line.
Data
If your system has an API, we read from there. Whether it has one, we clarify before the quote.
Ownership
Source code in your repository, logins on your accounts
Scope
No minimum. A single form is a job too.

05 / Live

What applies once the software is live.

Your drivers work nights too, and then the app has to manage without us. For everything else, the contract says when we can be reached, how fast we respond and where your data is stored.

Reachable
Daily from 6 a.m. to 11 p.m.
Response
Within 3 hours, guaranteed by contract
Warranty
24 months on defects
Backups
30 days, encrypted and stored separately
Servers
In Düsseldorf or Frankfurt

06 / What it costs

What an app for your operation costs.

We bill by the hour, there’s no minimum. Bremshelfer was finished after one month. The project assistant gives you a rough range for your project in four questions, without you leaving any contact details.

Hour of work
€130 + VAT
Intro call and cost estimate
€0

Every payment comes after a sign-off. You can step out between any two milestones.

Cost estimate in four questions ↗

07 / How it works

Two days of watching first, then we build.

Before we build, we spend two days at your operation and watch how the work gets done. That’s where the specification and the quote come from. Then we build in one-week sprints, and at the end of each week you see a demo.

  1. 01First contact
  2. 02Analysis
  3. 03Requirements
  4. 04Quote
  5. 05Contract
  6. 06SpecificationFrom here we build
  7. 07Sprints
  8. 08Launch
The full process ↗

08 / Questions

Questions before you get in touch.

What is a rail operator (Eisenbahnverkehrsunternehmen, EVU)?
An EVU runs trains. It provides locomotives, wagons and staff and takes freight or passengers to their destination. The network it runs on is operated by an infrastructure manager (Eisenbahninfrastrukturunternehmen, EIU). So software for an EVU is about trains, vehicles and staff, not track and signal boxes.
Have you worked for a rail operator before?
Not as a client job. Bremshelfer is our own product, built with a train driver. What we build for rail operators is on this page as an offer. Projects from other industries show how we build APIs and portals.
Does it work with our dispatch system?
If your dispatch system has an API or exports data as a file, we read from there. Whether that works, we clarify before the quote, with you and, if needed, with the vendor. We don’t want to replace it.
Does it work without a signal?
What’s needed out on the line, yes. Bremshelfer calculates entirely on the device. Forms and reports stay on the phone until there’s a signal again, and then they go out. What’s only needed in the office runs in the browser.
Who checks that the rules are right?
You do. The rules come from your rulebook, and someone from your operation checks the results against their own. With Bremshelfer, that was a train driver. At the end of each week you see a demo and check it before we go on.
What does it cost?
The intro call and cost estimate cost €0. After that we bill by the hour, €130 + VAT per hour of work. There’s no minimum, a single form is a job too.

Tell us briefly about your project

The intro call costs nothing, and neither does the cost estimate after it. If what you need can be bought off the shelf, we tell you its name and send no invoice.

Start a project

We usually reply the same business day