Channel
@gifs_en
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
9,971subscribers
-53 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001311307171 |
|---|---|
| Type | Channel |
| Username | @gifs_en |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/gifs_en |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 14:00 | 9,971 | -7 |
| 14 Sept 2026, 16:39 | 9,978 | -4 |
| 11 Sept 2026, 01:22 | 9,982 | -9 |
| 6 Sept 2026, 06:38 | 9,991 | +2 |
| 1 Sept 2026, 18:53 | 9,989 | -16 |
| 31 Aug 2026, 20:25 | 10,005 | -1 |
| 30 Aug 2026, 20:25 | 10,006 | +2 |
| 29 Aug 2026, 20:55 | 10,004 | -4 |
| 28 Aug 2026, 23:37 | 10,008 | -2 |
| 28 Aug 2026, 00:27 | 10,010 | +1 |
| 27 Aug 2026, 03:56 | 10,009 | +3 |
| 26 Aug 2026, 04:03 | 10,006 | -5 |
| 25 Aug 2026, 02:15 | 10,011 | -7 |
| 23 Aug 2026, 17:17 | 10,018 | -3 |
| 22 Aug 2026, 03:34 | 10,021 | -1 |
| 20 Aug 2026, 16:57 | 10,022 | +1 |
| 19 Aug 2026, 16:02 | 10,021 | +5 |
| 18 Aug 2026, 16:33 | 10,016 | +5 |
| 17 Aug 2026, 16:36 | 10,011 | -9 |
| 16 Aug 2026, 08:47 | 10,020 | first reading |
20 posts held, back to 17 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pages 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 2 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
😱 Ark Invest just dropped some wild numbers In 2025, AI-generated words officially outnumbered words written by humans — for the first time in history. At this pace, AI will surpass the entire 500-year archive of human-written text before 2030. And it's already reshaping Telegram. Channels are quietly replacing human editors with automated tools — and one of the most interesting examples is @morty, built by the @ma…
Almost imperceptibly.💦
The helmet didn't save him.
Athlete
Shawarma for men💪🏻
Barbershop💈
Someone got badly burned.
Rotten🥴
Unexpected ending
Got outed by mom.😅
Cool game🔥
Nice shot🤣
Showing the 12 most recent of 20 posts we hold for @gifs_en. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 24 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Funny Gifs” (@gifs_en), 9,971 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/gifs_en.
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.