Telegram RegisterThe public register of Telegram
Telegram profile photo for OFST

Channel

OFST

@GameOSTfr

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,396subscribers

+96 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001605658027
TypeChannel
Username@GameOSTfr
DescriptionGame/Movie/TV Soundtracks Archive List: t.me/GameOSTfr/57847 Zip Files: https://t.me/OFSTzip Requests: @Sirout + Channel Direct
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 September 2026
Last confirmed live30 September 2026
Measurements held15
On Telegramt.me/GameOSTfr

Topic

Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,3001,3961,3486 August 2026 — 1,300 subscribers9 August 2026 — 1,313 subscribers12 August 2026 — 1,346 subscribers15 August 2026 — 1,363 subscribers17 August 2026 — 1,372 subscribers20 August 2026 — 1,373 subscribers23 August 2026 — 1,374 subscribers26 August 2026 — 1,373 subscribers29 August 2026 — 1,379 subscribers4 September 2026 — 1,380 subscribers10 September 2026 — 1,387 subscribers13 September 2026 — 1,391 subscribers17 September 2026 — 1,392 subscribers25 September 2026 — 1,396 subscribers30 September 2026 — 1,396 subscribers6 August 202630 September 2026
15 measurements spanning 55 days, net +96. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,286–1,410 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 02:541,396no change
25 Sept 2026, 04:181,396+4
17 Sept 2026, 06:011,392+1
13 Sept 2026, 13:181,391+4
10 Sept 2026, 01:011,387+7
4 Sept 2026, 09:371,380+1
29 Aug 2026, 12:141,379+6
26 Aug 2026, 13:521,373-1
23 Aug 2026, 23:371,374+1
20 Aug 2026, 16:151,373+1
17 Aug 2026, 21:421,372+9
15 Aug 2026, 00:371,363+17
12 Aug 2026, 02:221,346+33
9 Aug 2026, 07:511,313+13
6 Aug 2026, 10:531,300first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 30 September 2026 — this entry's latest reading, not the date you are reading this.

“OFST” (@GameOSTfr), 1,396 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/GameOSTfr.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.