Telegram RegisterThe public register of Telegram

Channel

Tofublog

@Tofu_Blog

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

311subscribers

+0 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-1001935916086
TypeChannel
Username@Tofu_Blog
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/Tofu_Blog

Growth

3117 Aug 2026, 03:46 — 311 subscribers7 Aug 2026, 13:33 — 311 subscribers7 Aug 2026, 03:467 Aug 2026, 13:33
2 measurements taken within a single day. 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 310–312 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 13:33311no change
7 Aug 2026, 03:46311first reading

Engagement

17 posts held, back to 19 July 2026the 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 · 30 days
57.5%
avg views ÷ 311 subscribers
Avg views / post
179
17 posts measured
Reaction rate
3.67%
reactions ÷ views · ER floor
Posts in window
17
of 17 held

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. It is computed over the 16 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held17 (19 July 20263 August 2026)
Views total3,042
Reactions total105
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:46 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.

Reaction mix

105 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 78.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8278.1%
🔥1211.4%
😁98.57%
❤‍🔥10.952%
🥰10.952%

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 16 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 105reactions 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 19 July 2026 to 3 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.

Recent posts

3 Aug 2026, 20:10 UTC84 views3 reactionsread 7 August 2026
Forwarded from @barkrayPhoto

Среда · 05.08 · 19:00 На связи - СИНDИКАТ! Мы готовы снова сотрясти танцполы, принося с собой волны беспощадного звука и безудержной энергии! 🔥 ЯРОСТЬ НА БИТЕ Погрузитесь в глубины Drum and bass! ZLODEEV · N-BORN · AGAROS SCREAM · BIPOLAR · BASSFACE SOLNTSE RADOST · PSYKOTEKNOLOGY 💀 ТОКСИЧНАЯ СТАДИЯ Для ценителей бешеного и разрушительного темпа HARDCORE! FATIMA HARIJAR · RANCOR SPIKE DIAS SIX · LACASKA · TOFUBO

3

2 Aug 2026, 20:05 UTC138 views13 reactionsread 7 August 2026
Photo

Сегодня отмечается день железнодорожника, с чем поздравляю всех причастных!!! А это кабина поезда, на котором мне очень хотелось бы проехаться за управлением. К сожалению, реализовать это практически нереально, но, кто знает, что ждёт впереди…

13

31 Jul 2026, 18:55 UTC166 views15 reactionsread 7 August 2026
Photo

Даже когда отпуск, ты продолжаешь работать.. В этом году исполняется десять лет ночной экскурсии по метро. В честь такой круглой даты организовано торжественное мероприятие, на которое меня позвали поучаствовать в роли диджея. Хоть тут и просто необходимо включать треки по сценарию, а не сводить треки, это всё-равно очень круто, наконец, две профессии пересекаются. А пока мероприятие не началось, немного шалю 😁

15

30 Jul 2026, 07:55 UTC198 views11 reactionsread 7 August 2026
Photo

Сижу, смотрю ютубчик, как вдруг… Вот такие приветы из прошлого))

😁92

29 Jul 2026, 08:37 UTC205 views1 reactionsread 7 August 2026

Кто хочет хорошо провести выходные, вот инвайт на беседу мероприятия, заходите: https://t.me/+AE4C7s0pdMg0ZmZi

1

29 Jul 2026, 08:16 UTC173 views2 reactionsread 7 August 2026

🍸 ДВА ЭТАЖА — ОДНА ТУСА 🍸 Друзья, мы любим размах, поэтому готовим кое-что масштабное! Впервые в истории наших вечеринок — ЦЕЛЫХ 2 ЭТАЖА для вашего комфорта и бесконечного движа. Уже 1 АВГУСТА!! 📍 Gusto Lounge Адрес: Большая Спасская, 8, стр. 1А ⏰ Старт в 19:00 и до самого утра. Что тебя ждёт на двух этажах: 1 ЭТАЖ — ГАСТРО-БАР 🍔 Вкуснейшая еда — горячие закуски, авторские блюда, всё для сытного вечера; 🍹

2

26 Jul 2026, 08:28 UTC184 views4 reactionsread 7 August 2026
Video

Одна ночь, две тусы, один посыл: разнести танцпол. С задачей успешно справился, всем спасибо 🤩

4

24 Jul 2026, 19:51 UTC191 views6 reactionsread 7 August 2026
Video message

Video message, posted without a caption

4🔥2

24 Jul 2026, 18:34 UTC184 views2 reactionsread 7 August 2026
Video message

Video message, posted without a caption

2

22 Jul 2026, 13:54 UTC198 views7 reactionsread 7 August 2026
Forwarded from @LACASKAPhoto

TOFUBOI Диджей, который наводит суету на мероприятиях бомбической прямой бочкой, знакомыми мелодиями и невероятным драйвом. В эту ночь вас ждёт интересный сет, который, словно стук колёс, будет пробивать вашу душу изнутри — это гарантировано 😎 RAZZGON: MASTERPIECE OF SHIT 🗓 24 июля 📍 Бар 3.14 ЗДА | ул. Фридриха Энгельса, 21 🕥 22:00–6:00

7

22 Jul 2026, 12:35 UTC159 views6 reactionsread 7 August 2026
Video message

Video message, posted without a caption

3🔥3

22 Jul 2026, 08:12 UTC183 views2 reactionsread 7 August 2026
Forwarded from @subversionpromoPhoto

🖤РОЗЫГРЫШ 5 БИЛЕТОВ 🖤 24 июля состоится SUBVERSION: ACT III в баре «Край» — мы решили разыграть 5 билетов Условия участия: — быть подписанным на SUBVERSION — отметить «Я в деле!» под этой публикацией Участвуй — объявим результаты 24 июля в 18:00 @subversionpromo

2

Showing the 12 most recent of 17 posts we hold for @Tofu_Blog. 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.

Citation-graph rank

Citation-graph rank — 639,872 of 1,169,250entries 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.

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.

Mentions

Named by 7 registered channels — 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.

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.

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

“Tofublog” (@Tofu_Blog), 311 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Tofu_Blog.

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.