Telegram RegisterThe public register of Telegram
Telegram profile photo for bot_program < 5 >

Channel

bot_program < 5 >

@expeditionsmp_bt_5

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

27subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003594851529
TypeChannel
Username@expeditionsmp_bt_5
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/expeditionsmp_bt_5

Growth

2712 Aug 2026, 01:31 — 27 subscribers12 Aug 2026, 19:06 — 27 subscribers12 Aug 2026, 01:3112 Aug 2026, 19:06
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 26–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:0627no change
12 Aug 2026, 01:3127first reading

Engagement

19 posts held, back to 27 June 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
116.7%
avg views ÷ 27 subscribers
Avg views / post
31.5
2 posts measured
Reaction rate
11.1%
reactions ÷ views · ER floor
Posts in window
2
of 19 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 July 2026
Posts held19 (27 June 202631 July 2026)
Views total63
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 01:31 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

80 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 27.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👾2227.5%
custom 53774946001580431942126.3%
custom 52944276992704090041721.3%
custom 5413422912122139406911.3%
custom 541379056991261162278.75%
custom 541388598690605873322.50%
custom 541597712058313562422.50%

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 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 12 of the 19 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 80reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 27 June 2026 to 31 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.

Recent posts

31 Jul 2026, 18:29 UTC16 views6 reactionsread 12 August 2026

#public_function() { . ° . 。° ✨*。. .<мне бы ноги как у всех>. . . 。°✨. ✨° . ° }

👾2custom 53774946001580431942custom 54137905699126116222

20 Jul 2026, 09:50 UTC47 views1 reactionsread 12 August 2026
File

File, posted without a caption

custom 53774946001580431941

15 Jul 2026, 22:18 UTC82 views13 reactionsread 12 August 2026
Photo

#void_function() { .<справедливость>. }

custom 54134229121221394068custom 54137905699126116223custom 54138859869060587332

8 Jul 2026, 18:53 UTC71 views8 reactionsread 12 August 2026
Photo

#private_function(var condition) { > . . . . ⚠️ WARNING ⚠️ . !CRITICAL ERROR . < Принудительная перезагрузка системы . ожидание . > . < wait . > . < wait . . > . < wait . . . > . < ошибка перезагрузки системы . выполняется проверка файлов . > 🕐 . < обнаружены повреждённые данные . выполняется форматирование повреждённых ячеек памяти . > 🕐 . < форматиров

👾3custom 53774946001580431943custom 54159771205831356242

4 Jul 2026, 21:37 UTC75 views18 reactionsread 12 August 2026
Photo

#public_function() { . <Немезида> сегодня пострадал . опять . нет глаза . . <грусть> . ВЫВОД . <голоса аномалии> нельзя доверять . . дом безопасен . аномалии дома = небезопасно . . убрать аномалии с <Д0М 35> . . убрать тех кто взаимодействует с аномалиями . . <Сиерра> обезопасить и помочь . 🕐 . <Сиерра> не называл никак <Спаркл> . . не <запрещаете думать> . . <Сиерра> выдвинул предположение . почему надо ругать

custom 52944276992704090046custom 53774946001580431946👾5custom 54134229121221394061

3 Jul 2026, 21:10 UTC52 views11 reactionsread 12 August 2026
Photo

#public_function() { . <Сиерра> очень устал сегодня . . много людей и очень шумно . <херобрин> аномалия . 🕐 . люди бегали у огня и поджигались . <Сиерра> устал тушить . если <Карл> говорит не <таскать> его почему люди берут его на руки . вопрос . . зачем мучить <Карл> . вопрос . . очень много людей дома . очень шумно . }

custom 52944276992704090045👾3custom 53774946001580431943

3 Jul 2026, 17:15 UTC15 viewsread 12 August 2026
Forwarded from @F404PAINcom

➿➿➿➿➿➿➿➿➿➿➿ 🤩 Фокстрот, Сиерра и Стратт официально назначены старшими ботами с сегодняшнего дня😊 ➿➿➿➿➿➿➿➿➿➿➿

3 Jul 2026, 15:16 UTC24 viewsread 12 August 2026
Forwarded from @NEMESISENIFexp

0Г0НЬ П0 БЛЯДСК0Й С0Б4КЕ.

3 Jul 2026, 12:24 UTC26 viewsread 12 August 2026
Photo

💛💛💛💛💛💛💛💛💛💛💛 📃 #БальныйЗал 🌟🌟🌟 _Лог: 010 _Бекрумсы: Снова Аткрыты Для Всех _Вниматильна Асматрити Их Полнастью _Это Очинь Важна _Новые Комнаты Могут Быть Спрятаны В Старых Каридорах И Комнатах ☺️ 💛💛💛💛💛💛💛💛💛💛💛

1 Jul 2026, 22:46 UTC44 views3 reactionsread 12 August 2026
Photo

#private_function() { INSERT INTO Database VALUES (. люди вредят себе чтобы им было лучше . . люди действительно очень странные . . помогает с нагрузкой на нервные клетки .) ; 🕐 !ПРЕДПОЛОЖЕНИЕ . . . <<ДАННЫЕ НЕДОСТУПНЫ>> . . . }

👾1custom 52944276992704090041custom 53774946001580431941

Showing the 12 most recent of 19 posts we hold for @expeditionsmp_bt_5. 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 — 730,090 of 1,480,975entries 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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“bot_program < 5 >” (@expeditionsmp_bt_5), 27 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/expeditionsmp_bt_5.

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.