Firstly, because of the physical functionalities, FBS requires the actual distance between the operating stations and also calculates the statistics based on these distances. In some existing traffic contracts, however, calculations are made according to individual kilometres which do not correspond to the distances.

Since April 2019, it has therefore been possible to store the "tariff kilometres" in the FBS infrastructure data and use them in the statistical evaluations of the timetables. For this purpose, you will find a column entitled "Tariff-km" in the list of operating locations of the infrastructure data. The entry of tariff kilometres is optional. They are also only used in the statistical evaluations. If no tariff kilometres have been entered, the actual distances in the statistics will be calculated as usual.

Tariff kilometres can only be entered for operating locations. For further statistically relevant points, "placeholder" operating locations may have to be added. Usually it should be sufficient to enter tariff kilometres for stations. For all operating locations in between, FBS automatically interpolates the corresponding value (grey font colour).

In the statistics settings, you will find an option for selecting the distances used. Here you can choose whether the FBS statistics should be calculated with tariff kilometres or with the actual distances.

The special function available since January 2010 on the register page cross-section allocation, used to be able to calculate the apparent operational performance ("train-km") for such cases, becomes an obsolescence model by the possibility to store tariff kilometres in the infrastructure data. For the sake of completeness, however, it should not be left unmentioned:

In the iPLAN statistics, there is the cross-section assignment tab page. This table shows the number of trains for each track section of the network. A single breakdown of the trains of a section is displayed when a certain section is selected.

With this window, it is possible to calculate operating performances in FBS which do not refer to the actual distances. To do this, you can enter an external section length for each section of the cross-section table (double-click on a line, enter key or right mouse button). So that the section lengths entered in this way do not expire after closing the window, you can save them in a simple text file (right mouse button). The assignment of the external section lengths to the track sections is done by the complete description of the section. If a section is divided by changing the route (new train, run section) (e.g. before Göschwitz < --> Saalfeld, afterwards Göschwitz <--> Rudolstadt and Rudolstadt <--> Saalfeld) or summarized, the resulting new external section lengths must be added manually. Since such tariff kilometres are often not proportional to the distance, the program does not undertake any calculations of its own.

This functionality is a compromise not to overburden FBS with "non-technical" (arbitrary) contexts. When used in a reasonable manner, e.g. with TPS-kilometres, a smooth working is possible. Each individual section length must be entered only once; the section boundaries shift only rarely.

It is assumed that differing kilometres with more consistent use of computing technology will not occur again in the timetabling process (for example, they will be corrected in the case of new contracts for transport contracts).