TrueVirus

🚅 SRTO Update 0.5.1 Release date: 08.10.2026 The SimRail Track Overview has been updated to the version 0.5.1. The update is live and available at https://simrail-expert.de/projects/srto What this update includes: added a missing line marker at Grodzisk Mazowiecki on Screen 4 added both missing line makers at Galkowek on Screen 4 fixed wrong UTC time offset for servers PL1, PL2 and PL5 moved the marker [G] at Grodzisk Mazowiecki on Screen 4 to the lower track changed wrong entry signal at Bednary changed logic for if a server is offline, the player count in the server list will be set to 0 added a number in the server list of how many players are online in SimRail besides the percentage Thanks to everyone who reported those issues. Much appreciated. Because I forgot to mention it in the last post/update: SimRail-Expert now has a small Community Discord! It's not big, and there is not much activity going on right now, but that can change with your participation. The servers main purpose is to share informations about ongoing updates, but also to get in touch with you on simple chats, questions about upcoming features and updates, and you are also able to post bug reports and discuss such reports with me and other users. Obviously, you are not required to join the server or be especially active, but I would much appreciate it if you join the server. This would help me and the project by a lot! 😇 You can join by clicking on this link: https://discord.gg/BZszjfaFPu Happy SimRail-ing! 🚉

🚅 SRTO Update 0.5.0 Release date: 02.10.2026 It's here! I'm happy to finally announce the release of version 0.5.0 of the SimRail Track Overview. It was a long stretch, with a lot of headaches, long days and even longer nights. But now it's finally here! 📋 A brief overview of what has changed With this version, the SRTO is no longer available on GitHub Pages. It now runs on its own platform, which gives me more control over the website and its content. The SRTO is also part of, and the beginning of, a future idea: the newly founded domain SimRail-Expert. 🌐 What is SimRail-Expert? SimRail-Expert is planned to become a small hub for tools like the SRTO, plus a few other small additions, for example a "Signals Guide". These additions and planned tools are still in development, so the SRTO is the only available tool for now. But stay tuned for what's to come! The new version of the SRTO is available at https://simrail-expert.de/ 🔌 SimRail-Expert's own API The new hosting also makes it possible to run a self-hosted API endpoint, which provides the SRTO and future tools with additional information. IMPORTANT! The API endpoint is only allowed to be used by tools hosted at simrail-expert.de External usage from other websites is forbidden! 📝 The Changelog ✨ New feature: Timetable Delta Time This new feature works together with the new and own api of SimRail-Expert. It will show the timetable delta of any train right on the screen at the tail of the train in minutes, either with a plus or minus as prefix. If a train is right on time, there is no number visible. Due to this new feature, all of the tracks had to be remade and all screens had to be realigned to fit the new wider layout. This results in the previous 2 screens now being split into four screens: S1: Katowice <-> Włoszczowa Północ S2: Włoszczowa Północ <-> Warszawa S3: Sędzice <-> Łódź North / Gałkówek (missing the connection between Kutno and Lowicz Glowny) S4: Rozprza <-> Pruszków 🖥️ UI Rework The UI has finally been reworked to its full potential. The currently selected screen is now visible in the header, with the clock aligned to the right. The selection of Screens and Servers is still in panels, but now aligned to the right underneath the button itself. The screen list now shows the start and end of the screen, as well as a brief overview of the route the screen covers. Available servers are now categorized into "Polski", "German", "International", and "Additional Server". Each server now also shows the current number of players in trains and stations, as well as the amount of all players online and the usage in percent. 🗺️ Map Changes As already written above, all the screens have now a different look due to the new, larger track layout 1️⃣ Screen 1 — Katowice <-> Włoszczowa Północ Added a short section of LK138 towards Szabelnia / Mysłowice Tracks between DG and DZA are now "shifted" to better represent the placement of signals and platforms as they are in the game 2️⃣ Screen 2 — Włoszczowa Północ <-> Warszawa Added station "Żyrardów" to the screen Reworked station "Grodzisk Mazowiecki" Reworked station "Pruszków" 3️⃣ Screen 3 — Sędzice <-> Gałkówek The Łódź North region has been added to this screen. It's positioned below the rest of the screen. The additional track between Kutno and Łowicz Główny will be added in a later update Reworked the APO "Męka" Reworked the APO "Kolumna" and "Dobroń" Reworked "Łódź Kaliska" Reworked "Łódź Widzew" 4️⃣ Screen 4 — Rozprza <-> Pruszków Rozprza and Piotrków Trybunalski are now next to each other Koluszki and Skierniewice have been re-created from the ground up. Some differences are still there, but they are not very noticeable Grodzisk Mazowiecki and Pruszków have been added to the screen 🤓 Some small nerdy information (just skip this if you're not into technical stuff) Besides having SimRail as one of my favourite games and being very interested in trains, I love to code things. And one part of doing all this is to learn and develope my knowledge of programming. Those last 2 months, I learned a lot, and I used that knowledge in this update. Every update will develop my skills, and I use those skills to make any project on SimRail-Expert better and better. This version features a whole refactor of the projects folder and file structure as well as naming, data structure and custom hooks. One think I'm very proud of is the new map data structure. I was able to reduce the lines of code (loc) from 28.582 loc (version 0.4.2) down to 27.322 loc with the small reminder that the whole Lodz North area has been added and that everything had to be redone. So I think this is a massive improvement. The way I was able to reduce the loc was to create custom drawing commands which then get parsed into Canvas Path2D, as well as combine the "annotation" elements. So instead of having about 30 elements in the annotation array, one element taking up 7 lines, I now have maybe about 30 to 50 lines for the same amount of information. Also, all the map data is now "chunked" into separate files, each of them get fetched at runtime. This reduces the main.js file by a big margin to how it was before. Okay, enough nerdy informations... 😅 🏁 Final words This update took a lot of time and effort to make due to the map redesign. But I'm happy to finally releasing it. I hope you're happy with the update! 😇 And thank you to everyone who's using the SimRail Track Overview while playing SimRail or just to see what's on the tracks. I appreciate everyone! Much love! Happy SimRail-ing! 🚉

Development Update – SRTO is becoming SimRail-Expert First of all, I want to apologize for the long silence about the SRTO. A bigger update is on the way, and with it comes an important change. SRTO will no longer be hosted on GitHub Pages. From now on, it will move to its new home: SimRail-Expert, a new name and domain that naturally grew out of the project's development. SimRail-Expert has already been set-up and is running the same version as GitHub Pages. Alongside the move, SRTO is receiving a completely refreshed and more consistent user interface. The screens have been redesigned to support one of the upcoming features: Visible Train Delays, making delay and early-running information directly visible on the map. Looking further ahead, SimRail-Expert is intended to become a small hub for multiple SimRail-related tools and utilities, with SRTO being the first part of that larger vision. The new Visible Train Delays feature is powered by SimRail-Expert's own API, allowing timetable delay information to be integrated directly into SRTO. More details and the next update are coming soon. 😉

🚆 SRTO Update — v0.4.1-alpha | Small fixes A small updates just released. It's addressing wrong map data. 🔧 What's changed: fix: changed wrong signal types at station Góra Włodowska and Korytów fix: fixed wrong station prefix for Łódź Marysin add: added break marker between Łódź Widzew and Łódź Marysin Small side note: I had to change the already pushed v0.4.1 update due to the additional information about the wrong signals at Korytow. Was a bit stressed, but I got it right. (i hope) 🙂 And thanks to LeProblemo for reporting those issues. Appreciate you!

Unfortunately, this is not a "bug". It is just how the map works and the data is being published by SimRail. If a train has more than 5 kilometers to the next signal, the data simply returns "null", so there is no information on the next signal. The way the train still gets shown on the map is by predicting the next signal which in this case is only "2439_LC_Z2" because left track usage can't be predicted. This is why 154035 shows over 412032 cause his signal is more than 5 kilometers away despite driving on the left track. I could've made some kind of extra logic to it to prevent wrong prediction, but this can cause more wrong predictions. And why train 154035 has overridden train 412032 visually is because I haven't accounted that in the new logic of 2 trains having the same SignalInFront. The new update has a new logic checking which train is closest to the next signal if two trains share the same signal (commonly caused by a train passing a red ABS signal). But I haven't accounted for this kind of situation where a train has "null" as SignalInFront given. But I appreciate your report! It still is a bug report regarding two trains sharing the same signal with one train having "null". I will note that. Thank You! 🙂

🚆 SRTO Update — v0.4.0-alpha A new major update for SRTO is now available! This release brings the second screen of the Łódź Voivodeship close to completion and introduces a new quality-of-life feature: player names in the train hover tooltip. ✨ Added 🗺️ Second Screen Expansion The second screen has now been completed in its current form. It now includes: Koluszki Skierniewice the remaining section of the line up to the entry signals of Grodzisk Mazowiecki Please note: This layout is still subject to change. I am planning to increase the spacing between tracks, so both the first and second screen will receive significant visual changes over the next updates. 🚆 Player Names Train hover tooltips now display the name of the player currently driving the train. Dispatcher names are planned for a future update and will appear in a dedicated information tooltip for each signal box or dispatching station. 🔧 Fixes & Improvements Signal Boxes Reworked the appearance of signal box symbols. Added proper rotation so they now match the dispatcher's operating direction - thanks to Pospec76502 for making this suggestion! User Experience Added a "New Version" notification. Existing users will automatically be informed about new releases. First-time users will not receive the notification. Added a Changelog page, accessible from the Options menu. Map Improvements Added the missing "Józefinów" label. Added the missing switch at Łódź Lublinek - thanks to GoDaddy for reporting this issue Corrected the position of the Opoczno Południe signal box - thanks to Pospec76502 for reporting this issue Added the missing po for Łódź Radogoszcz Zachód between Łódź Żabieniec and Zgierz. Removed the destination texts "to Koluszki" and "to Gałkówek" and added the missing Żakowice po. Fixed incorrect signal names between Zawiercie and Góra Włodowska / Myszków - thanks to LeProblemo for reporting this issue Fixed an issue where two trains occupying the same signal could cause the wrong train to be rendered. The map now correctly displays only the train closest to the signal - thanks to DazT for reporting this issue 🛣️ Roadmap – What's Next? The next updates will mainly focus on improving the readability of the track layout. Instead of using 60 px per track, I decided to increase the spacing to 100 px per track. This will provide enough room for future gameplay features, such as displaying train delays and additional operational information without cluttering the map. You can already see this new layout around Koluszki and further towards Żyrardów, and it will gradually be applied to the rest of the map. Planned Feature: Train Information Window Another feature currently in development is a movable train information window. Clicking on a train will open a small draggable panel that keeps all relevant train information visible, eliminating the need to keep hovering over the train. 📋 Trello Roadmap If you're interested in everything that's currently planned for SRTO, be sure to check out the Simrail-Expert Trello Board, where I regularly update upcoming features, ideas, and development progress. ❤️ Thank You! As always, thank you to everyone testing SRTO, reporting bugs, suggesting new features, and providing feedback. Your support and ideas continue to shape the project, and every report helps make SRTO better. 🚉 Looking forward to hearing what you think about v0.4.0-alpha!

Yeah, I witnessed it myself several times. The problem is that the signal names are wrong ingame. Normally, every ABS signal has a naming system Line_Mileage, so for example L4_2203, but for some reason, the signal is named L1_2203 ingame. I will fix those 3 segments you gave me as well as several other ones that might be wrong named. Just gonna check every signal then, why not. But this will take some time. I have too much going on currently. Yeah, I can do that indeed. Already planned to rework the symbols because they are a little bit tooo big 😅 And the orientation is a thing I can do for sure, why not 😉

Hey peoples, sorry for the lack of updates recently. The motivation wasn't really high the last few days and some private stuff came across my life, so yeah. But I made a lot of progress the last few times I worked on this project. Koluszki and Skierniewice are fully made, so I just need to connect everything, copy Grodzisk, Pruszkow and Wlochy and then the second screen should be finished. But the update still has to wait a few more days because I need to update some features and the code itself. But I try to be as fast as possible. 😉

Hey, appreciate your kind words! Yes, this is a global problem which can happen on every signal. The way I render the trains is that I take the train, get the Signal, look into my data if I have this signal, get the coordinates and then place the train. What I have not made yet is that kind of detection system that if 2 trains have 1 signal in common which I will rework the logic in the next update. But thanks for the heads up! The next update is published as soon as the second screen is completely finished. This will of course take some time because I have to create both Koluszki and Skierniewice which are very big stations 😅 I think this will be done about next week. Hope I can make this happen 🙂

🚆 SRTO Update — v0.3.2-alpha A small update is now available with added missing platforms, plus a few fixes. ✨ Added • Added missing platforms between Sędzice and Pabianice This addition stretches the whole top row all the way to the right and completes it • Added missing platforms for:  — Pabianice Północne  — Łódź Retkinia  — Łódź Pabianicka  — Łódź Dąbrowa  — Łódź Zarzew 🔧 Fixes & Improvements • Fixed the station name for Rozprza • Fixed the information text for “to Gałkówek” • Corrected signal placement for 2426_LCH_F and 2426_LCH_E at Łódź Chojny As always, feedback and bug reports are appreciated — thanks to everyone helping improve SRTO! 🚉

Nah, you're good. Well, a "veil" or just borders you can drag would indeed be much easier than spacing the rows, but some rows do slightly overlap with others. And about that station thing: I'm not really sure what you mean by that. By creating a selectable list where the user can select or "enable/disable" stations and/or abs-tracks, this would achive exactly this. And by enabling the option "Extended View" you can drag it yourself wherever you want it. What I really can't do is to move for example Dabrowa Gornicza to the right of Bedzin because everything has kind of it's designated place. If I want to do something like that, I need to make a "shift"-value for every data node and say "if Bedzin, then shift this, if so then so" and so on. And that would make a big mess in logic and data. A friend of mine used to just open two windows and align them next to each other, one showing for example Lazy Lc - Lazy (B) and the other one Lazy La, looking then like this: I then had the idea of just rendering a second screen right next to each other, with either a simple line between them or just no line. You can then adjust both views seperatly and align them next to each other. This idea would make a "Dabrowa Gornicza next to Bedzin" simple, but the user has to do it himself instead of being a user-friendly option of "Show Dabrowa Gornicza next to Bedzin". Well, sometimes the user still has to do something and can't fully rely on the person making the application. This would also result in the data being exactly the same. The is no de-synced data between two browser windows and the Header/Footer would also be only one. What do you think about this idea of two screens being next to each other on the same website?

I think you probably mean space between each row. That would be possible indeed, and a dragable cover to hide things at the top and/or bottom can also be more or less included. I see what I can do. I will talk about that with some friends who use this application as well and what they think about your ideas! 👍🏻 But any changes to the actual screen will also be changes to either heavy logic or actual data editing. So for example, moving the "rows" to make more space between them can only be done either actually editing the data or making a variable and option to move the rows by user-defined values. As I already said, I will talk about that with some friends :) What I can't do is make space between the tracks, because for that, I basically have to "redraw" and reposition everything 😅

This is something on my list, but I'm not 100% sure how to do that. I need to probably change the data structure for that and make some changes to it. I have a look into it on how I'm gonna be able to do something like this, but I'm not sure when this feature will be available. I have the same thought the whole time, but I am not able to do something like this. I don't have any informations on set routes of any signal. I can only predict those via the signal speed, but there are a lot of possible routes where you only drive 40 or 60 km/h. So sadly no, a visible route is not possible. I only have the next signal, the speed of that given signal and the distance between the train and the signal. If the developers every decide to publish such information on given routes, for example a full `signals-open` api, then yes, this would be a feature which will definitly be in this application. But right now, sadly not. I'm sorry 😕

The long awaited update has finally arrived! The SRTO has finally updated to version 0.3.0-alpha! Available HERE What's new in this update? [Changelog] ➕ A new screen has been added. It's observing the Łódź Voivodeship, currently expanding towards Koluszki. To change the screen, simply click on the Button "Change Screen" ➕ A new feature "Flip Screen" has been added in the options. This will flip the whole screen to align better with dispatching panels. Additional Changes: The settings menu has been slightly reworked Border-Tracks (Brynow, Myszkow etc.) have been changed to "dotted" lines Some trains going out of border will now be visible instead of just "vanish" (not all) the Bridges between Dąbrowa Górnicza Ząbkowice and Łazy Łc have been reworked a bit added Dąbrowa Górnicza Huta Katowice, Przemiarki and LCS Starzyny into the first screen Edit: Yes, I know that there are missing platforms on the top tracks of the Łódź Voivodeship (between Sierad & Zdunska Wola). I might update them soon in the next few days. :) For a full changelog, visit the CHANGELOG.md in the GitHub Repository! Like everytime, I appreciate every feedback you can give me, either here as a normal reaction or message, or in the GitHub Repository. Any feedback does help me moving further in this project. Thank You! <3

A "Flip Screen" option has been implemented but is not live. It will be published with the next update which will be pushed next week I think. Right now I'm preparing the next screen which will be the Lodz Voivodeship, beginning at Sedzice all the way down to Warszawa. This will probably take some time I will also make a few tweaks to already existing tracks, for example the bridges between Dabrowa Gornicza Zabkowice and Lazy LC. I need to rework that, it looks so awful tbh 😂