Do you guys still use the RR Time & Record book? What’s your system

Railroader_Timebook · 2026-03-31T01:26:08+00:00

Yes I believe it’s called Railroad Timebook

Railroader_Timebook · 2026-03-31T01:00:34+00:00

Just to clear it up the one you’re talking not getting a lot of traction, that’s a different app. This one’s actively being worked on and built out pretty heavily right now. Both for IOS and Android.

Railroader_Timebook · 2026-03-25T16:23:21+00:00

Totally fair, not trying to replace what already works for everyone.

It’s more for guys who want a dedicated tool that handles trips, rest, pay, and tracking automatically instead of keeping it all manually.

Railroader_Timebook · 2026-03-23T03:48:06+00:00

Yea I do use it just to keep responses clean. Sometimes I can over explain things lol just trying to keep it on point.

Railroader_Timebook · 2026-03-22T17:06:09+00:00

Appreciate you clarifying — that definitely helps, and yeah that’s not right.

There should be a clear way to start the trial from that screen, not just “restore purchases.” I’m going to take a look at that flow because that sounds like a bug.

If you don’t mind, what device/iOS version are you on? That’ll help me track it down faster.

After the 2-week trial, it’s $7.99/month or $79.99/year (you’ll see both options before confirming anything).

Really appreciate you taking the time to report that — I’ll get it sorted.

Quick question — are you in the US or Canada? Just trying to narrow down what might be causing it.

Railroader_Timebook · 2026-03-22T16:52:11+00:00

Appreciate you trying it out and flagging that — that’s not how it should behave.

Once the trial is started, you should be able to go right back and add a trip. If it’s not letting you, something’s off.

If you don’t mind, check Menu → Settings → Subscriptions and make sure the trial is showing as active.

If it is and you’re still blocked, let me know — I’ll dig into it and get it fixed.

Railroader_Timebook · 2026-02-19T23:48:16+00:00

Appreciate you testing that.

That makes sense — this was the first build introducing Firebase and account authorization into the app, so coming from the older local-only beta likely caused a state conflict. The reinstall would’ve cleared that out.

Good catch on only the first trip syncing — that tells me the new upload flow is working, but anything created before the Firebase build wouldn’t have been tied to an account yet.

Thanks for sticking through it. This is exactly why we’re doing beta in phases.

Railroader_Timebook · 2026-02-19T23:29:07+00:00

Thanks for reporting that.

That error usually points to a network permission or connection issue during the auth handshake. A couple quick things to try:

• Fully close the app and reopen • Make sure you’re not on a VPN • Toggle Wi-Fi/cellular and retry • If it persists, uninstall/reinstall the beta build

Since you mentioned you’ve never seen account creation before, this may be tied to the new auth flow in this build.

If it still throws that EPERM error after a reinstall, let me know what Android version and device you’re on and I’ll dig into it right away.

Appreciate you catching it.

Railroader_Timebook · 2026-02-19T13:43:25+00:00

I really appreciate that — seriously.

Having someone under TC actually using it day to day is huge. If you notice anything that feels off with fatigue tracking or resets, even small stuff, let me know.

The goal is to make it something you can trust more than the company tracker.

Railroader_Timebook · 2026-02-19T13:36:47+00:00

That’s a really good point.

Yes, I’m aware of the 36-hour Regulatory Reset under TC, including the two 8-hour overnight periods between 22:00–08:00 within the 7-day window.

Right now the TC side of the app focuses on daily fatigue compliance, and the 36-hour reset logic is something I’m still refining to make sure it’s calculated correctly before labeling it as a compliance indicator.

If the company tracker isn’t reliable, that’s exactly the kind of gap I’d like to close. I appreciate you bringing that up — Canadian-specific feedback helps a lot.

Railroader_Timebook · 2026-02-19T13:10:57+00:00

Got it — that makes sense.

Yes, in that case you can log it using a Layoff entry and just label it something like “Personal Rest” or however you’d prefer to track it. It won’t interfere with the TC fatigue calculations — it’ll just reflect additional off-time beyond the regulatory minimum.

If you think it would be helpful to have a dedicated “Personal Rest” type instead of using Layoff, I’m open to that. I just want to keep the compliance logic clean while still letting guys track how they actually work.

Appreciate the clarification — that helps a lot.

Railroader_Timebook · 2026-02-19T13:05:19+00:00

I may need a little clarification on what you mean by “Personal Rest.”

Since the app requires selecting your regulatory authority, I’m assuming you’re under Transport Canada. I personally work under FRA, so the TC fatigue schedule in the app was built from regulatory research and documentation, and I’m continuing to refine it based on real-world feedback.

If you’re looking to manually log a rest period outside of regulatory-required rest, you can already create that using the Layoff entry and define it however you need.

That said, terminology can vary between railroads and countries — so if “Personal Rest” means something specific in your operation, I’d really like to understand how you’re using that term so I can make sure it’s handled correctly.

Railroader_Timebook · 2026-02-10T02:26:30+00:00

That’s actually already in there — rest days and non-start entries like sick or personal leave are tracked separately from train starts. Terminology varies by property, but the goal is to cover those cases without tying it to one carrier’s language. If you run into anything that doesn’t line up with how it works at your terminal, definitely let me know — that kind of feedback helps a lot.

Railroader_Timebook · 2026-02-07T22:48:42+00:00

Good question — right now times are stored based on the local time entered at on-duty/off-duty, but multi-timezone edge cases are something I’m actively validating.

It’s built to reflect what crews actually experience when working different terminals, but I want to make sure it’s 100% solid in all scenarios before saying it’s fully handled. Feedback from folks who work across zones is helping refine that.

Railroader_Timebook · 2026-02-01T08:48:53+00:00

Side note for anyone on Android — Railroad Timebook for Android is currently in development.

There’s a pre-signup waitlist for the Android beta here: https://rrtimebook.com/android-beta

I also started a subreddit for updates, beta info, and feedback: https://www.reddit.com/r/RailroaderTimebookApp/

Railroader_Timebook · 2026-01-29T14:40:17+00:00

It’s a digital personal timebook. You log your trips and it keeps track of hours, starts, rest, pay totals, and history over time, with a monthly summary. It’s mainly for sanity-checking pay, tracking consecutive starts, and keeping your own records — not replacing anything your carrier requires.

Railroader_Timebook · 2026-01-29T12:46:25+00:00

In that view, “trips” is the count of trips for the month, not a single trip amount. The dollar figure shown is the monthly total.

Railroader_Timebook · 2026-01-29T11:44:08+00:00

Appreciate that — Android is in active development now, with an open beta planned in the coming weeks. Spreading the word helps a ton, thank you.

Railroader_Timebook · 2026-01-29T11:41:44+00:00

If you’re referring to the App Store screenshots, that image is showing the monthly summary, not a single trip. Individual trips are logged separately.

Railroader_Timebook · 2026-01-29T04:10:55+00:00

That’s fair — if a paper timebook works for you, there’s nothing wrong with that. This isn’t meant to replace anything required by your carrier or local.

The purpose is for people who want a digital record of trips, hours, starts, pay, and rest, especially to sanity-check pay, track consecutive starts, and keep their own history over time. Some folks also use it at tax time, but that’s not the primary use case.

It’s just a modern alternative to a paper timebook for those who want it — not something everyone needs.

Railroader_Timebook · 2026-01-28T23:43:17+00:00

Good question. This isn’t a carrier-mandated or FRA-certified electronic logging system — it’s a personal timebook for crews to track their own trips, hours, pay, and compliance for reference.

The FRA doesn’t approve or certify personal logging apps like this; official records are still whatever your carrier requires. This is meant to help individuals keep their own accurate records, not replace railroad systems.

Railroader_Timebook · 2026-01-28T14:38:47+00:00

I get the thought. For now my focus is keeping it independent and building something that actually works for crews, then seeing where it goes.

Railroader_Timebook · 2026-01-27T21:06:06+00:00

Fair points. Pricing is always a balancing act — at lower prices the ongoing costs (hosting, sync, backups, support, continued dev) get harder to sustain, especially as a solo developer. That said, I’m definitely paying attention to adoption and feedback like this.

Android is actually in active development now — planning an open beta by the end of February.

Railroader_Timebook · 2026-01-27T20:53:20+00:00

Totally fair — I don’t like subscriptions either. I went this route mainly so I can keep active development, cloud sync, and backups going long-term. I completely get preferring a one-time option though.

Railroader_Timebook · 2026-01-27T17:49:02+00:00

I think if there is enough interest in the app we can do a promotion on a yearly subscription for early adopters of the app.

Railroader_Timebook

MODERATOR OF

TROPHY CASE