Channel
@funyafanclub
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
77subscribers
-28 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003984884087 |
|---|---|
| Type | Channel |
| Username | @funyafanclub |
| Created | Between 1 April 2026 and 24 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/funyafanclub |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 11:36 | 77 | -3 |
| 8 Sept 2026, 08:39 | 80 | -19 |
| 29 Aug 2026, 07:36 | 99 | -1 |
| 22 Aug 2026, 10:58 | 100 | -4 |
| 15 Aug 2026, 11:22 | 104 | -1 |
| 9 Aug 2026, 09:02 | 105 | no change |
| 8 Aug 2026, 06:32 | 105 | first reading |
10 posts held, back to 24 July 2026 — 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 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 10 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
217 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 35.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5388970121412772999 | 76 | 35.0% | |
| custom 5276153777362055748 | 63 | 29.0% | |
| custom 5393062374842320234 | 24 | 11.1% | |
| custom 5321040785515241692 | 18 | 8.29% | |
| custom 5336974036146612961 | 17 | 7.83% | |
| custom 5211226911367257670 | 16 | 7.37% | |
| custom 5233493005377241899 | 3 | 1.38% |
Custom emoji. Every row above is a 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 9 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 217 reactions 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 24 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.
пусть все ваши печали унесут радужные единороги аминь🦄🍼🌈
custom 53889701214127729995custom 53930623748423202342custom 52112269113672576701custom 52334930053772418991
🦄🦄🦄🌈🌈🌈🌻🌈🌻🍀🍀🍀❤️🩹❤️🩹☮️❤️🩹☮️🦄🦄🍀🦄🍀
custom 539306237484232023413custom 53889701214127729999custom 52112269113672576706custom 52334930053772418992
пиривет я очень старалася комментарий реакция репост пжпжжпжп
custom 538897012141277299917custom 52112269113672576709custom 53930623748423202349
канао больше ни частный 🎉 ПРОВЕДЕНЫ НЕКИЕ РЕФОРМЫ рип клуб анонимных алкоголиков
custom 527615377736205574815custom 53369740361466129617
цр6ытгштыл втлыштцтш😀 переходник @funyafanclub
custom 527615377736205574811custom 53889701214127729996custom 53369740361466129614
кто хочет трейд
ну вот всьо типерь пишите добрые слова... переходник @funyafanclub
custom 538897012141277299912custom 52761537773620557489custom 53210407855152416928
wip анимаш по персам моей подружкньки няки !!! переходник @funyafanclub
custom 53889701214127729998custom 52761537773620557483custom 53210407855152416922
пириодически zабываю об этомканале!🌟 переходник @funyafanclub
custom 538897012141277299916custom 52761537773620557489custom 53210407855152416927custom 53369740361466129611
реквестуны итд кому надо в лсик za файликом ;) переходник @funyafanclub
custom 527615377736205574816custom 53369740361466129615custom 53889701214127729993custom 53210407855152416921
Showing the 10 most recent of 10 posts we hold for @funyafanclub. 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.
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.
Named by 1 registered channel — 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“перееzд///zакрыто 🦄” (@funyafanclub), 77 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/funyafanclub.
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.