Channel
@fourfiftysixthoughts
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
330subscribers
-4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002883940763 |
|---|---|
| Type | Channel |
| Username | @fourfiftysixthoughts |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/fourfiftysixthoughts |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 00:38 | 330 | -1 |
| 24 Aug 2026, 05:16 | 331 | -1 |
| 16 Aug 2026, 07:36 | 332 | -2 |
| 8 Aug 2026, 07:05 | 334 | no change |
| 8 Aug 2026, 06:30 | 334 | first reading |
15 posts held, back to 2 August 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 15 (2 August 2026 – 7 August 2026) |
| Views total | 930 |
| Reactions total | 237 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07:05 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 3 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.
305 reactions across 13 posts, in 16 distinct kinds. The most used accounts for 17.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 52 | 17.0% | |
| 😭 | 46 | 15.1% | |
| custom 5379982344000145669 | 41 | 13.4% | |
| custom 5213035728254037133 | 28 | 9.18% | |
| custom 5217938424832491948 | 26 | 8.52% | |
| 💔 | 24 | 7.87% | |
| 🍓 | 22 | 7.21% | |
| 😁 | 15 | 4.92% | |
| ✍ | 14 | 4.59% | |
| custom 5215188151114425253 | 10 | 3.28% | |
| 🥰 | 9 | 2.95% | |
| 🤝 | 7 | 2.30% | |
| custom 5420134124939674314 | 4 | 1.31% | |
| custom 5195229094492534058 | 3 | 0.984% | |
| ⚡ | 3 | 0.984% | |
| 🔥 | 1 | 0.328% |
Custom emoji. 6 of the rows above are 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 13 of the 15 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 305 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 2 August 2026 to 7 August 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.
КСТАТИ, ни у кого не видела подобную мысль, поэтому вот вам внезапный вкид (и откид) Малышка буквально является напоминанием, что именно Ки-Хун пережил и как. Неизвестно, как отреагирует психика настолько сломленного и покалеченного человека — Ки-Хун вполне легко может возненавидеть малышку за то, что она выбралась оттуда, что он сделал и отдал ради этого, и почему она вышла, а его близкие нет. Его не совсем здорова…
💔22❤3
Пидорасы ебаные, я спинофф про Ин Хо теперь не увижу никогда
😭20❤3
Многие не готовы это услышать, но я скажу Даже если бы Ки-Хун выжил с ребёнком на руках и выбрался с игр, он не стал бы её воспитывать, заботиться и так далее, просто потому что его истощенная психика и истощенное тело не позволили бы ему это. Ки-Хун сам еле как справлялся с тем, чтобы заботиться о себе и делать базовые вещи - есть, пить, ходить в душ, выходить на улицу и так далее. Если бы не цель в виде поиска Вер…
custom 521793842483249194826custom 54201341249396743144custom 52151881511144252532❤1
Казань тоже любит ИнХунов, приезжайте
❤24🥰8
Пов Ки-Хун и жена Ин Хо встретились в загробной жизни (этот идиот проебал вообще всех и всё)
😭26⚡3
Я чертовски скучаю даже по этому долбоёбу
custom 537998234400014566928
Привет как дела
custom 537998234400014566912custom 51952290944925340582custom 52130357282540371332
Привет а ты чем болеешь
✍14custom 52130357282540371334custom 52151881511144252534💔2🔥1🥰1
Пока что это лучшее что я видела за последний месяц
😁15custom 52130357282540371335custom 52151881511144252534custom 53799823440001456691
ЭТО ВОСХИТИТЕЛЬНО
🤝7
ГОСПОДИ
Я КРИЧУ ЧАЙКОЙ
Showing the 12 most recent of 15 posts we hold for @fourfiftysixthoughts. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“456 мыслей | squid game” (@fourfiftysixthoughts), 330 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/fourfiftysixthoughts.
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.