Telegram RegisterThe public register of Telegram
Telegram profile photo for Dr¡ // пожизненный полурест

Channel

Dr¡ // пожизненный полурест

@DriFool

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

45subscribers

-4 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002424674177
TypeChannel
Username@DriFool
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/DriFool

Growth

45494710 August 2026 — 49 subscribers10 August 2026 — 48 subscribers10 August 2026 — 48 subscribers24 August 2026 — 47 subscribers1 September 2026 — 46 subscribers9 September 2026 — 45 subscribers10 August 20269 September 2026
6 measurements spanning 30 days, net -4. 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 44–50 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 13:3845-1
1 Sept 2026, 04:1346-1
24 Aug 2026, 14:0447-1
10 Aug 2026, 12:4848no change
10 Aug 2026, 11:4148-1
10 Aug 2026, 06:0149first reading

Engagement

20 posts held, back to 17 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 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

174 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 20.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54228966908541183963520.1%
custom 54632580576077607273419.5%
3319.0%
💘137.47%
custom 5375302169677296945126.90%
👾105.75%
🕊105.75%
custom 522205516387061695195.17%
custom 522432334039460186252.87%
🍓52.87%
🔥31.72%
🤗31.72%
🌭10.575%
💯10.575%

Custom emoji. 5 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 18 of the 20 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 174 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 17 July 2026 to 9 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

9 Aug 2026, 19:28 UTC22 views15 reactionsread 10 August 2026

тест реакт

custom 52220551638706169518custom 52243233403946018624custom 54228966908541183963

9 Aug 2026, 19:25 UTC22 views3 reactionsread 10 August 2026

инфопост переделан ща будут новые реакты

3

9 Aug 2026, 18:54 UTC26 views7 reactionsread 10 August 2026

хочу канал переоформить можно? 🥺

4🍓1💘1🕊1

9 Aug 2026, 18:53 UTC27 views11 reactionsread 10 August 2026
Photo

что б не было пусто так и быть выложу скетч осторожно есть шанс что вытекут глаза

5custom 54228966908541183962🕊1custom 52220551638706169511custom 52243233403946018621custom 54632580576077607271

4 Aug 2026, 10:01 UTC48 views3 reactionsread 10 August 2026

напишите под этим постом что бы вы хотели видеть в канале может арты по каким то фд или что то такое а то актив упал мне грустна шо делать

👾3

2 Aug 2026, 14:56 UTC56 views9 reactionsread 10 August 2026

подвожу итоги артфайта 7 атак защит с моей стороны и 9 атак защит на меня маловато конечно но для первого раза я думаю сойдёт, учитывая что почти все мои работы полноценки крч мне оч понравилось в след году надеюсь отрисовать больше атак!!!!!

custom 546325805760776072752👾1custom 53753021696772969451

2 Aug 2026, 14:21 UTC54 views9 reactionsread 10 August 2026
Photo

еще одна скетч защита но мне не нравится пох

custom 54228966908541183966custom 54632580576077607272custom 53753021696772969451

2 Aug 2026, 13:30 UTC43 views7 reactionsread 10 August 2026
Photo

скетчевая защита а еще пожалуйста наставьте реактов на предыдущую картинку я старалась над ней оч🥺

🍓2💘2custom 53753021696772969451custom 54228966908541183961custom 54632580576077607271

1 Aug 2026, 20:00 UTC43 views1 reactionsread 10 August 2026

теперь у меня будут заказывать коммишки? и желательно оплачивать их... пожалуйста...

🍓1

1 Aug 2026, 19:51 UTC55 views12 reactionsread 10 August 2026
Photo

защищаюсь от ликвы

🕊5custom 54228966908541183964custom 54632580576077607272custom 53753021696772969451

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

Forward network

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.

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.

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

“Dr¡ // пожизненный полурест” (@DriFool), 45 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/DriFool.

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.