Telegram RegisterThe public register of Telegram
Telegram profile photo for Eurofurence Notifications

Channel

Eurofurence Notifications

@efnotifications

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

8,214subscribers

+634 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001027864291
TypeChannel
Username@efnotifications
Created23 January 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/efnotifications

Growth

7,5808,2147,8976 August 2026 — 7,580 subscribers7 August 2026 — 7,582 subscribers9 August 2026 — 7,592 subscribers13 August 2026 — 7,605 subscribers16 August 2026 — 7,647 subscribers19 August 2026 — 7,840 subscribers23 August 2026 — 8,000 subscribers27 August 2026 — 8,055 subscribers29 August 2026 — 8,114 subscribers1 September 2026 — 8,186 subscribers5 September 2026 — 8,202 subscribers10 September 2026 — 8,214 subscribers6 August 202610 September 2026
12 measurements spanning 35 days, net +634. 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 7,485–8,309 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 17:198,214+12
5 Sept 2026, 08:558,202+16
1 Sept 2026, 12:548,186+72
29 Aug 2026, 15:388,114+59
27 Aug 2026, 02:028,055+55
23 Aug 2026, 17:498,000+160
19 Aug 2026, 18:267,840+193
16 Aug 2026, 20:267,647+42
13 Aug 2026, 08:537,605+13
9 Aug 2026, 23:467,592+10
7 Aug 2026, 00:507,582+2
6 Aug 2026, 16:067,580first reading

Engagement

72 posts held, back to 23 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 18 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
55.9%
avg views ÷ 8,214 subscribers
Avg views / post
4,590
43 posts measured
Reaction rate
1.50%
reactions ÷ views · ER floor
Posts in window
43
of 72 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 23 August 2026
Posts held72 (23 July 202623 August 2026)
Views total197,520
Reactions total2,957
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 19:04 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.

What this channel posts

Video runtime
5m 04s
Average length
2m 32s

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.

Reaction mix

5,841 reactions across 72 posts, in 47 distinct kinds. The most used accounts for 51.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3,03051.9%
👍71612.3%
🔥4297.34%
🤡2293.92%
🤣1672.86%
❤‍🔥1532.62%
🗿1282.19%
🎉1252.14%
👀931.59%
😍811.39%
🥰580.993%
🤨530.907%
😱490.839%
🫡450.77%
🌚380.651%
👎350.599%
🆒320.548%
🍓320.548%
🤔300.514%
🦄300.514%
27 further kinds2884.93%

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

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

23 Aug 2026, 23:11 UTC≈4,200 views74 reactionsread 28 August 2026

For those at the Alternative Dead Dog Party at the CODA Club: The Club kindly asks to not bring their glasses outside, please transfer the drinks to plastic ones at the door. Thank you!

👍3712🗿11🆒5🍓4🤝3🎃2

23 Aug 2026, 12:04 UTC≈4,960 views61 reactionsread 28 August 2026
Photo

Looking for the Dead Dog Party shuttle? Follow the flag! It’s right outside the Radisson, near the bus stop. The first shuttle starts moving at 16:30, departing every 20 minutes until 21:00. For the way back, you can find the shuttle stop outside the Docks to the right of the entrance - starting at 22:00 with a last course at 02:30, every 20 minutes - stopping at the Intercity hotel before finishing in front of the

45👌10👍6

23 Aug 2026, 11:25 UTC≈4,800 views81 reactionsread 28 August 2026

🐾 Nothing to do before the Dead Dog Party? We need your paws! Teardown is in full swing, and we still need Critters to help us carry, sort, and get the CCH back in shape. There are many open shifts. Sign up here: https://critter.eurofurence.org/⁠ Every helping paw makes a difference, thank you! ❤️ And to all our Critters... You Rock!

67👍4🗿4❤‍🔥3🦄3

23 Aug 2026, 10:17 UTC≈4,820 views27 reactionsread 28 August 2026

🔐 Security Lost & Found is now open! Lost items can be collected at Check-In 2 in the CCH until 14:00 today. Please stop by to retrieve your belongings.

17👍10

22 Aug 2026, 15:59 UTC≈4,950 views22 reactionsread 28 August 2026

⏱️ SCHEDULING 📅 Schedule Change: Pawpet Show: The Truest Crime has been updated: Saturday, 22 August at 19:00 → Saturday, 22 August at 19:30

🤡14👍53

22 Aug 2026, 15:59 UTC≈5,040 views38 reactionsread 28 August 2026

⏱️ SCHEDULING 📅 Schedule Change: Closing Ceremony has been updated: Saturday, 22 August at 18:00 → Saturday, 22 August at 18:30

🤡20🤣6👍53🐳3🤬1

22 Aug 2026, 15:59 UTC≈5,090 views43 reactionsread 28 August 2026

⏱️ SCHEDULING 📅 Schedule Change: Closing Ceremony – Overflow has been updated: Saturday, 22 August at 17:30 → Saturday, 22 August at 18:00

🤡324👍4🌚3

22 Aug 2026, 15:58 UTC≈4,690 views22 reactionsread 28 August 2026

⏱️ SCHEDULING ✨ New Event: Closing Ceremony – Overflow II will take place in Arena Stage – CCH Hall H Section 1-2 starting at 18:30 on Saturday, 22 August

👍10🤡4🤪4😭3🤣1

22 Aug 2026, 15:58 UTC≈4,550 views6 reactionsread 28 August 2026

⏱️ SCHEDULING 📅 Schedule Change: Closing Ceremony – Overflow has been updated: Saturday, 22 August at 18:00 → Saturday, 22 August at 18:30

👍6

22 Aug 2026, 15:54 UTC≈4,630 views73 reactionsread 28 August 2026

We currently setup an additional closing ceremony overflow screening in Arena Stage: Hall H - this does add some additional Delay but will allow fore more furrys to see the show!

🎉2312🤡11👍7🗿7😁5😭5🤔3

22 Aug 2026, 15:52 UTC≈5,070 views20 reactionsread 28 August 2026

For anyone who didn’t manage to pick up their items at the Convention Store, we’ll offer an additional pickup opportunity today from 19:00–21:00 in Hall 1, Cloakroom Foyer, Level 1 (near the elevator). This includes: Pre-ordered T-shirts Sponsor Package Super Sponsor Package If you haven’t collected your items yet, please stop by during the pickup window.

15👍5

22 Aug 2026, 14:32 UTC≈4,340 views11 reactionsread 28 August 2026

🔔 Fursuit Badges Correction: - On-site orders and printing is still available till 1900/7pm

👍11

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

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

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

“Eurofurence Notifications” (@efnotifications), 8,214 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/efnotifications.

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.