WOODHOUSEThe Loftwah Software Factory

Find a project or subject.

15 pages in the index

Esc closes search ⌘ K or Ctrl K opens it

MoreMenu
Measurement & privacyGames × RadioExplore connected productsEdition discoveryExplore the projects

Analytics

Each project on its own relevant measure

Custom dates
UTC · max 90 days
24 Sept 2026 – 23 Oct 2026 · 30 days · Today is partial0/0 reporting projects for this measure · 1/1 sources reporting · Saved snapshot

This report is frozen at 2026-10-23 04:50 UTC. Refresh these dates · Latest 30 days

Game starts · Games

Count per UTC day · gaps mean unavailable

A recorded launch into gameplay. Repeat play counts again. These are browser reports, not verified players.

No daily measurements for this selection

Choose another measure, project or date range. An unavailable source does not mean nobody used the product.

No line is drawn for missing data.

Chart data & export

These are daily values for game starts. A dash means unavailable. Daily distinct-browser counts must not be added to estimate period-level people.

Game starts· UTC dates ·count
Date
2026-09-24
2026-09-25
2026-09-26
2026-09-27
2026-09-28
2026-09-29
2026-09-30
2026-10-01
2026-10-02
2026-10-03
2026-10-04
2026-10-05
2026-10-06
2026-10-07
2026-10-08
2026-10-09
2026-10-10
2026-10-11
2026-10-12
2026-10-13
2026-10-14
2026-10-15
2026-10-16
2026-10-17
2026-10-18
2026-10-19
2026-10-20
2026-10-21
2026-10-22
2026-10-23

Can we compare these dates?

Coverage for the selected measure. Colour describes evidence, not popularity.

Comparable full dayPartial dayLegacy / test riskBounded / sampledNot measured
24 Sept 202623 Oct 2026

No clean full-day comparison is available for this selection in this snapshot. First collection days and today remain partial. Legacy activity may include tests that cannot be separated.

Have browsers come back?

These are optional browser signals, kept separate for each project. They cannot identify people or establish cohort retention. Daily browser counts do not add up to a period total.

  • WoodhouseNot measured for these dates

    DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill. Optional browser measurement has not yet received a consenting visit; browser counts are unavailable. Browser measures cover opt-in visits only and remain partial. Private project-scoped visit associations expire after 90 days; a window intersecting expired history is unavailable. Browser totals use retained period DISTINCT counts, never daily sums.

What changed around this activity?

Dated release observations sit beside the collection and comparison boundaries reported by each source. Nearby dates suggest questions to investigate; they do not show that a release caused a change in use.

This is a reviewed selection, not a complete release feed. Notes are frozen with the report and may precede the selected dates; notes after its last selected day are omitted.

Explore 2 dated release and collection notes
  1. Woodhouse · Collection began

    First source-reported collection date. Earlier activity is unavailable; the first day may be partial.

  2. Woodhouse · Comparison boundary

    The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.

Follow the numbers to their source

Every measure has a definition, a collection boundary and blind spots.

Woodhouse4 measures available

Live aggregate endpoint · generated

Collection began
2026-10-15T00:00:00.000Z
Comparable history from
2026-10-15T00:00:00.000Z
Source revision
Not supplied
  • Exact accepted event counters, not unique humans or anti-cheat proof. Blocking, opt-out, offline play and automated traffic affect coverage.
  • DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill.
  • Current UTC day and collection-start day may be partial. Cross-device retention, cohort retention and acquisition sources are not measured.
  • Optional browser measurement has not yet received a consenting visit; browser counts are unavailable.
  • Browser measures cover opt-in visits only and remain partial. Private project-scoped visit associations expire after 90 days; a window intersecting expired history is unavailable. Browser totals use retained period DISTINCT counts, never daily sums.
Visits 3,896Reported activity
One accepted visit marker per tab session; sessions reset after 30 minutes idle. Reloads in the same session do not add visits. Not distinct people.
Engaged sessions 42Reported activity
One accepted marker per tab session after at least 10 seconds of active product use. Foreground, unpaused and recent trusted input required.
Active time 42m 44sReported activity
Accepted 1–30 second foreground, unpaused activity increments, ending 30 seconds after trusted input. Server bounds total by session wall time. Radio time is excluded.
Project discoveries 18Reported activity
Accepted deliberate clicks from Woodhouse to a published project destination. Counts clicks, not visits received by that project.
Reporting browsers —Not measured
Distinct optionally consenting, project-scoped browser tokens with accepted visits in the selected UTC window. Period DISTINCT, not a sum of daily browser counts. Tokens rotate after 90 days; resets, multiple devices and privacy choices prevent interpreting these as people.
Returning browsers —Not measured
Distinct optionally consenting browser tokens with a visit in this UTC window and an earlier different accepted tab session in retained 90-day history, including same-day returns. Period DISTINCT, not a sum of daily returns. This is not cohort retention; expired earlier visits and token rotation hide returns.

What am I looking at?

A recorded launch into gameplay. Repeat play counts again. These are browser reports, not verified players.

The chart uses one measure and one unit at a time. Each coloured line belongs to a project; the source totals cover the selected window.

What does it tell us?

This selection cannot currently establish a pattern of use.

No clean growth comparison yet. New collection and legacy test traffic limit the history we can trust.

Last complete week

The most recent complete Monday–Sunday UTC week for each project's own headline measure, against the week before. A record needs exact daily history for two adjacent complete weeks; this is a valid comparison, not only the large movements that raise an operational alert.

No project has two complete comparable weeks yet, so no week-on-week figure is shown. Collection is too recent to compare honestly, and nothing is inferred from it.

Why some projects are not compared (1)
  • Woodhouse: Fewer than two complete comparable weeks so far.

If you’re assessing the business

Early product instrumentation, with material evidence gaps.

Usage
0/0 projects reporting this measure. 1/1 sources provide some activity. Reports are not verified people.
Retention
No portfolio cohort-retention evidence. Returning browsers, where available, are a narrower signal.
Commercial proof
Revenue, paying customers, acquisition cost and customer value are not measured here.

Use this to ask better product questions. It cannot establish product–market fit, market demand or an investment case.

Read the product dossiers

Report details

Snapshot
78533b3457ba704d348cfc21
Captured
2026-10-23 04:50:18 UTC
Dates
2026-09-24 – 2026-10-23
Time zone
UTC; dates may differ from your local day
Tracking, retention & privacy choices