Переподписываемся
☃12💘3🎉2

Channel
@gasa4fanchannel
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
176subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001863288163 |
|---|---|
| Type | Channel |
| Username | @gasa4fanchannel |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/gasa4fanchannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 02:43 | 176 | no change |
| 11 Aug 2026, 19:45 | 176 | first reading |
17 posts held, back to 28 November 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 30 December 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
489 reactions across 16 posts, in 18 distinct kinds. The most used accounts for 21.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 103 | 21.1% | |
| 😢 | 77 | 15.7% | |
| 💘 | 67 | 13.7% | |
| 😭 | 51 | 10.4% | |
| 🙏 | 43 | 8.79% | |
| 😨 | 34 | 6.95% | |
| ☃ | 27 | 5.52% | |
| 🎉 | 27 | 5.52% | |
| ❤🔥 | 17 | 3.48% | |
| 😁 | 15 | 3.07% | |
| 🤩 | 14 | 2.86% | |
| 🥱 | 3 | 0.613% | |
| 🍓 | 2 | 0.409% | |
| 👎 | 2 | 0.409% | |
| 👏 | 2 | 0.409% | |
| 💊 | 2 | 0.409% | |
| 🕊 | 2 | 0.409% | |
| 🔥 | 1 | 0.204% |
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 489reactions 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 28 November 2024 to 30 December 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Переподписываемся
☃12💘3🎉2
★ знаете, когда я создавал этот, тогда ещё, конфешенс я был 11 летним ребёнком, которому настолько понравилась какая-то игра в роблоксе, что тот решил таким способом найти себе единомышленников. мне было так грустно от того, что я не мог найти русскоязычных фанов гаса4, что я решил взять на свои юные плечи ответственность за поиск и объединение их в один большой дружный коллектив. я тогда не думал, что количество под…
🙏43💘11😢9❤4❤🔥4👏2🕊2
★ мы очень надеемся что админы этого кф будут держать фандом в более надёжных руках! (нам не платили если что) ✩ 👾, #адм
😢26😨6☃3
★ Хорошая альтернатива: https://t.me/gasa4stixxal ✩ 🍰, #адм
❤17🎉1
Channel name was changed to «*:・゚✧ { закрыто } gasa4 fan channel»
★ привет, гаса4фк! спешим поздравить вас с наступающим новым годом и сообщить одну менее позитивную новость. к сожалению, мы с совлд всё же приняли решение о закрытии этого канала. временно или навсегда - ещё не ясно, но сейчас поддерживать жизнь гаса4фк как раньше выглядит для нас чем-то трудным и бессмысленным. вы, наверное, заметили, что наш канал сильно скатился вплане базовой работы и взаимодействия с аудиторией…
😢39😭23
Photo, posted without a caption
😭28💊2
#тейк : Хеееееее (cr: VictoriaMahh)
💘21🎉6☃2❤2👎2🔥1
★ #тейк : тгк @roryblehh
❤21☃5💘5🍓1🎉1😁1
★ #тейк : "Вафлл 0пять забыл" я не знаю чт0 мне делать с ивта8... в0т вам [п0ка чт0] п0следнее чт0 я рис0вала с эт0й ав [я не умею с тенями и свет0м раб0тать, с0рре] ...в принципе есть вариант написать п0лный л0р, н0 у меня 0с0б0 нет времени сейчас, + я 0б эт0м забуду как и всегда 0 разраб0тке плейза даже думать не х0чется. слишк0м сл0жн0... неан0н: @qqfis22
❤15☃2🎉1💘1
#тейк : Описание съел мой кот*
❤🔥13☃2❤2🎉2🍓1💘1
★ #тейк : мои кенты мразе вышли,а решила дропнуть Дамме
❤14🎉2☃1😁1
Showing the 12 most recent of 17 posts we hold for @gasa4fanchannel. 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 — 1,169,182 of 1,548,671entries 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.
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.
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.
“*:・゚✧ { закрыто } gasa4 fan channel” (@gasa4fanchannel), 176 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/gasa4fanchannel.
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.