Галактических Вам снов! ❤️
custom 58327025029354651536

Channel
@LongffellowHUB
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Declared links · Cite this entry
487subscribers
-3 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001924064752 |
|---|---|
| Type | Channel |
| Username | @LongffellowHUB |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 28 August 2026 |
| On Telegram | t.me/LongffellowHUB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 14:34 | 487 | -1 |
| 15 Aug 2026, 09:43 | 488 | -2 |
| 8 Aug 2026, 09:31 | 490 | no change |
| 8 Aug 2026, 06:30 | 490 | first reading |
10 posts held, back to 29 July 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 pageof 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 | 10 (29 July 2026 – 7 August 2026) |
| Views total | 878 |
| Reactions total | 63 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:30 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.
87 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 42.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5832702502935465153 | 37 | 42.5% | |
| custom 5866322098179280994 | 25 | 28.7% | |
| custom 5920515596088250243 | 14 | 16.1% | |
| custom 5884500392640780142 | 7 | 8.05% | |
| custom 5832260147073780752 | 2 | 2.30% | |
| custom 5861896014121667949 | 2 | 2.30% |
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 areTelegram’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 9 of the 10 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 87reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 29 July 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @LongffellowHUB. 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 10 most recent posts we hold for this entry, published 29 July 2026 to 7 August 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.
Галактических Вам снов! ❤️
custom 58327025029354651536
СМАРИТЕ ЧЕ НАШЕЛ!11!! 😊 Свяжите мне пожалуйста Жозефину 🤲 🌸 Узнать стоимость игрушек можно здесь Layuki Toys | Вязаные игрушки
custom 58327025029354651539custom 58618960141216679492
💀 Похоже, Dragon Age отправляется на очень долгий отдых... Господамы... Кажется, новости сегодня совсем не радостные. Если верить свежим заявлениям ветерана BioWare Марка Дарры, то в обозримом будущем никаких новых игр по вселенной Dragon Age ждать не стоит. И дело тут даже не в деньгах. После довольно прохладного приема и слабых продаж Dragon Age: The Veilguard в Electronic Arts, судя по всему, решили больше не рис…
custom 586632209817928099413
Photo, posted without a caption
custom 58663220981792809949custom 59205155960882502433custom 58322601470737807521
😮 Господамы, свершилось! Спустя более трех лет эксклюзивности VK Play легендарная Atomic Heart наконец-то добралась до Steam в России и странах СНГ 🎩 💰 Ultimate Edition со всеми DLC сейчас отдают со скидкой 60%. Цена вопроса всего около 2 тысяч рублей (или 14 тысяч тенге). НАКОНЕЦ ТО ПОИГРАЕМ 🤝 А где выгоднее всего пополнить Steam? Ну конечно же на ggcel ❤️ 🥂 Пополняй баланс Steam на ggsel 🚬 Затаривайся играми …
custom 58327025029354651536custom 58663220981792809943
Доброго утра! ✋ Желаю Вам удачного, легчайшего и мего продуктивного старта рабочей недельки! 👍
custom 592051559608825024311
НАВАЛИТЕ АКТИВА, ГОСПОДАМЫ! ❤️ ВЕДЬМАК 1 | ЧАСТЬ 3: КРИМИНАЛЬНАЯ ВЫЗИМА ВЕДЬМАК 1 | ЧАСТЬ 3: КРИМИНАЛЬНАЯ ВЫЗИМА ВЕДЬМАК 1 | ЧАСТЬ 3: КРИМИНАЛЬНАЯ ВЫЗИМА
custom 58327025029354651538custom 58322601470737807521
🎩 ШЕЙХИ, ДОЖДАЛИСЬ! Ну шо, мои дорогие... Я таки победил этот злосчастный монтаж. 😌 Полный ролик по второй главе первого Ведьмака наконец-то готов к употреблению и уже доступен для просмотра на Boosty! ⚔️ ⚔️ Это, пожалуй, самый жирный и трудоемкий выпуск за недавнее время. Вторая глава высосала из Деда все соки, литры кофе и пару десятков нервных клеток, но оно того определенно стоило 👍 Если давно хотели поддержать…
custom 58845003926407801427
Фух блять... заебала эта ебатория 👮
custom 58327025029354651538
Posted without readable text
Showing the 10 most recent of 10 posts we hold for @LongffellowHUB. 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.
Citation-graph rank — 49,461 of 1,628,524entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
3 URLs this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Longffellow HUB” (@LongffellowHUB), 487 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/LongffellowHUB.
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.