Telegram RegisterThe public register of Telegram
Telegram profile photo for FREE FIRE НОВОСТИ

Channel

FREE FIRE НОВОСТИ

@kyivskyi_ff

Has discussion group

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

3,500subscribers

+344 since we began measuring on 13 September 2026

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

Register entry

Telegram ID-1002377992377
TypeChannel
Username@kyivskyi_ff
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live5 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/kyivskyi_ff

Topic

Gaming — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

3,1273,5003,313.513 September 2026 — 3,156 subscribers15 September 2026 — 3,153 subscribers19 September 2026 — 3,127 subscribers29 September 2026 — 3,209 subscribers6 October 2026 — 3,280 subscribers13 October 2026 — 3,467 subscribers16 October 2026 — 3,445 subscribers19 October 2026 — 3,435 subscribers22 October 2026 — 3,421 subscribers25 October 2026 — 3,424 subscribers28 October 2026 — 3,437 subscribers31 October 2026 — 3,466 subscribers3 November 2026 — 3,468 subscribers5 November 2026 — 3,500 subscribers13 September 20265 November 2026
14 measurements spanning 53 days, net +344. 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 3,071–3,556 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 20:383,500+32
3 Nov 2026, 06:593,468+2
31 Oct 2026, 11:513,466+29
28 Oct 2026, 12:113,437+13
25 Oct 2026, 19:563,424+3
22 Oct 2026, 22:093,421-14
19 Oct 2026, 10:463,435-10
16 Oct 2026, 09:063,445-22
13 Oct 2026, 00:443,467+187
6 Oct 2026, 10:573,280+71
29 Sept 2026, 16:013,209+82
19 Sept 2026, 04:563,127-26
15 Sept 2026, 02:183,153-3
13 Sept 2026, 21:503,156first 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“FREE FIRE НОВОСТИ” (@kyivskyi_ff), 3,500 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/kyivskyi_ff.

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.