Telegram RegisterThe public register of Telegram

Channel

alliga пубфан офишл

@alligaga4

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

240subscribers

+1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003588224582
TypeChannel
Username@alligaga4
CreatedBetween 1 December 2025 and 18 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/alligaga4

Growth

239240239.56 Aug 2026, 20:48 — 239 subscribers7 Aug 2026, 02:33 — 239 subscribers7 Aug 2026, 07:50 — 240 subscribers6 Aug 2026, 20:487 Aug 2026, 07:50
3 measurements taken within a single day, net +1. 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 239–240 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 07:50240+1
7 Aug 2026, 02:33239no change
6 Aug 2026, 20:48239first reading

Engagement

10 posts held, back to 18 April 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
107.1%
avg views ÷ 240 subscribers
Avg views / post
257
3 posts measured
Reaction rate
31.8%
reactions ÷ views · ER floor
Posts in window
3
of 10 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 5 August 2026
Posts held10 (18 April 20265 August 2026)
Views total771
Reactions total245
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:33 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

856 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 34.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 522017491738274296429834.8%
custom 596760234046154881120023.4%
💘16619.4%
🎉14817.3%
custom 5388990363593631731263.04%
custom 5400013422928631648182.10%

Custom emoji. 4 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 10 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 856reactions 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 18 April 2026 to 5 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

5 Aug 2026, 16:01 UTC132 views73 reactionsread 7 August 2026
Video

Ребята извините мне пока нечего постить я еще делаю две коммишки 💔 как их завершу буду доделывать тот регретслоп с прошлого поста Пока что вот вам кусочек штуки которую я делала для мью с твиттера на день рожденя пару недель назад #пуб #анимация

custom 596760234046154881132💘21custom 522017491738274296419🎉1

26 Jul 2026, 18:56 UTC323 views87 reactionsread 7 August 2026
Video

КСТАТИ еще помимо коммишек время от времени делаю очередной регретслоп секунд на 30, уже сделано на процентов 60 🙂 вот один из спойлеров ну не дебилы ли

🎉39custom 522017491738274296425💘18custom 59676023404615488115

26 Jul 2026, 16:59 UTC316 views85 reactionsread 7 August 2026
Photo

Те самые халф бади коммышке что я брала сто лет назад (первые четыре) по пяцот рублей 🌊 о и еще одна фулл за сорок долларв о а также еще один ЮЧЧЧЧ умираю 🙂А пока что по обычному прайслисту коммишены всё еще открыты в закрепе, но через пару недель я планирую повысить ценник на рублей 500 каждый ИЗВИНИТЕВ кстати недо лого для коммишек как вам хорошее или

🎉34custom 522017491738274296427💘18custom 59676023404615488116

21 May 2026, 19:41 UTC850 views111 reactionsread 7 August 2026
Photo

возвращаюс в стройййй!!,!, куча пубов но я стараюсь разнообразия прибавлять постепенно #пуб #каспер #пест #сплит #ламперт #дисколайт #нулл

💘45custom 522017491738274296436custom 596760234046154881122🎉8

3 May 2026, 10:29 UTC802 views57 reactionsread 7 August 2026

Трейды пока что не беру, извините!! Но теперь думаю скоро открыть, я как-то даже не задумывалась раньше о них ехехе 🥹 но я принимаю реквесты в анонимку!! могу нарисовать все кроме ос

custom 522017491738274296428💘14custom 596760234046154881113🎉2

3 May 2026, 10:09 UTC778 views89 reactionsread 7 August 2026
Photo

цикл «гнев-стыд» #пуб хедканон + давно не рисовала их злыми ууууууууу 🤩

custom 596760234046154881137custom 522017491738274296432🎉14💘6

1 May 2026, 12:04 UTC692 views88 reactionsread 7 August 2026
Photo

дравин энетин ат дис поинт #пуб #нулл #мр

custom 596760234046154881144custom 522017491738274296422💘19🎉3

27 Apr 2026, 13:27 UTC632 views86 reactionsread 7 August 2026
Photo

зайцеовечка #пуб

custom 522017491738274296443custom 538899036359363173126🎉13💘4

24 Apr 2026, 00:50 UTC641 views82 reactionsread 7 August 2026
Video

всем привет я начала обучать иностранцев о том что такое бусти через делания ЮЧи и теперь у меня впервые чтото заказали с зарубежа 😁 штука для мьюшки с твиттера с пубом и его соной за 60 долларофффф (это где-то 24,84 рубля) #пуб #анимация .доступно еще 3 слота кстати

custom 596760234046154881141custom 522017491738274296427💘9🎉5

18 Apr 2026, 23:50 UTC678 views98 reactionsread 7 August 2026
Photo

всё спать 😴😴😴😴😴😴спа😴😴😴😴😴😴😴😴😴ть😴😴😴😴😴😴😴хррррррр хр хр хрррр😴😴😴😴 #пуб хррррр 😴😴😴😴

custom 522017491738274296439🎉29custom 540001342292863164818💘12

Showing the 10 most recent of 10 posts we hold for @alligaga4. 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 — 319,522 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 5 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.

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.

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.

“alliga пубфан офишл” (@alligaga4), 240 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/alligaga4.

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.