First run

RunForge

Training analytics from your Intervals.icu account. Connect your own Firebase project to sync across devices — or skip and use it locally right now.

Firebase console steps
  1. console.firebase.google.com → Add project (name it RunForge).
  2. Build → Authentication → Sign-in method → enable Google.
  3. Build → Firestore Database → Create database → production mode.
  4. Firestore Rules tab → publish the rule below.
  5. Settings → General → Your apps → </> Web → copy the firebaseConfig object.
rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /users/{uid}/{document=**} {
      allow read, write: if request.auth != null
        && request.auth.uid == uid;
    }
  }
}
RunForge

Training, measured

Sign in to sync your runs, settings and dashboard across devices.

RunForge
Training analytics
RunForge
Not synced
–fitness
Fitness score
—
—

This week

Dashboard

Drag the grip to reorder · tap ✕ twice to remove

Sync

Connect Intervals.icu in Settings, then sync to pull your training history.

Last 12 weeks

Best week This week Other weeks

Heart-rate zones

Run log

Data source

RunForge only reads your Intervals.icu activities. Nothing is written back.

Not connected.

Training goal

Sets the weekly-mileage bar that scores 100. Half is the default 50 mi/wk; marathon training runs 70; 5K training runs 30.

Weight

Goal 190 lbs. Weight next to mileage moves more than a score does.

No weigh-ins yet.

Account & data

How the score works

Anchor100 = 1:30 half @ 160 bpm
Pace40%
HR efficiency40%
Volume20%

Motivational, not scientific. Intervals.icu already computes CTL/ATL training load with better math — use that for decisions. This score exists to give the dashboard one headline number, with a band and an attribution so it can explain itself.

Widget library

Add what you actually look at. Drag the grip to reorder.