Telegram RegisterThe public register of Telegram
Telegram profile photo for Freech

Channel

Freech

@FreechPUBG

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

136subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002289667184
TypeChannel
Username@FreechPUBG
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/FreechPUBG

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

136137136.57 August 2026 — 137 subscribers8 August 2026 — 137 subscribers16 September 2026 — 136 subscribers7 August 202616 September 2026
3 measurements spanning 40 days, net -1. 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 136–137 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 17:40136-1
8 Aug 2026, 23:15137no change
7 Aug 2026, 15:12137first reading

Engagement

17 posts held, back to 14 January 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
34s
Average length
17s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

77 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 49.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54744049709146701153849.4%
custom 54741725229896430211620.8%
custom 5474651145555176688810.4%
custom 541345329472080265856.49%
custom 547467598764601309656.49%
custom 547437446376196525733.90%
custom 547423570195856885322.60%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 15 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 77 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 14 January 2026 to 16 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 17 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @FreechPUBG. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 17 most recent posts we hold for this entry, published 14 January 2026 to 16 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

16 Jul 2026, 15:25 UTC59 views4 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54744049709146701152custom 54741725229896430211custom 54746511455551766881

14 Jul 2026, 20:44 UTC61 views1 reactionsread 8 August 2026
Photo

Открыл перед удалением 👍

custom 54744049709146701151

18 Jun 2026, 06:59 UTC139 views3 reactionsread 8 August 2026

Кого не было Итоги: 62 открытия припасов: 2 ауга неоновых 1 свд 205 кейсов укрытия: 1 галил 2 чертежа Повезло или нет?

custom 54744049709146701152custom 54743744637619652571

17 Jun 2026, 09:16 UTC99 views2 reactionsread 8 August 2026

Напоминаю! Стрим сегодня будет после 23:00, будем крутить кейсики и посмотрим сам патч Заходите смотреть на мою боль или нереальную радость

custom 54744049709146701152

16 May 2026, 17:23 UTC176 views7 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54741725229896430215custom 54746511455551766881custom 54746759876460130961

8 Apr 2026, 12:02 UTC325 views7 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54744049709146701153custom 54742357019585688532custom 54746759876460130962

3 Apr 2026, 15:35 UTC247 views2 reactions1 Starread 8 August 2026
Video

Если не фейк, то надо проверить 😱

custom 54744049709146701152

7 Mar 2026, 15:19 UTC279 views5 reactionsread 8 August 2026
Photo

повезло повезло 😱

custom 54744049709146701153custom 54741725229896430211custom 54746511455551766881

3 Mar 2026, 18:58 UTC237 views10 reactionsread 8 August 2026
Photo

У нас пополнение! 🚨👽

custom 547440497091467011510

1 Mar 2026, 15:21 UTC180 views2 reactionsread 8 August 2026
Photo

С первым баном на твиче 🎉🎉🎉 Бан на 7 дней, подал апелляцию Надеюсь апрувнут Upd. Не апрувнули, чиллим недельку, может сделаю обучающие видосы, раз время есть

custom 54746511455551766882

9 Feb 2026, 16:31 UTC202 viewsread 8 August 2026

https://www.twitch.tv/freech1337/clip/FairStrangePheasantTwitchRaid-WY1KRB7_l3MIybao

Showing the 12 most recent of 17 posts we hold for @FreechPUBG. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“Freech” (@FreechPUBG), 136 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/FreechPUBG.

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.