Channel
@tAEw11s
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003976845232 |
|---|---|
| Type | Channel |
| Username | @tAEw11s |
| Created | Between 1 April 2026 and 18 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/tAEw11s |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:47 | 1 | no change |
| 13 Aug 2026, 06:03 | 1 | first reading |
20 posts held, back to 18 June 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 31 July 2026 |
|---|---|
| Posts held | 20 (18 June 2026 – 31 July 2026) |
| Views total | 39 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 13:47 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.
Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
@BERVSU — @Adenovskie_off рест 24.07 - 25.08 @ck_swan — @neroxu рест 20.07 - 29.07 @KRDMKL — @HMMLSK @BERVSU — @muveszeeti рест 24.07 - 25.08 @nahyyyyyyy — @Street_dance_channel рест 17.07 - 30.07 @SRN8XS — @ONLFAMILYOU рест 20.07 - 26.07 @SORTADLE — @chasovskieworld на днях перезаключили @vkvirz — @HALOR1A рест 24.07 - 01.08 @adsonsimm — @detxdom рест с 22.07 @DZ4MN — @SPUT1ON @mnkpaam — @luxarias122 рест с 01.07 (п…
Следящий: — @Gdarites Канал — @CDMS1M Пдп — 10:10 Папка — актив + рп Допы — @JosephJosten @OBSC1NO @doahve @volimmrr @KSLPTT @pdaora @JostenNoctar @donahwe @monahve 50 соо
— Канал : @ULTIMAclan — Следящий : @ULTIMAonkij — Папка : Актив+Рп — Пдп : 8:8 — Допы : @ULTIMAonkij @onsjsjdk @C3KC1CTT @uhhhnopls @kites104 @sodidoff @ME630W @weessiii 40 соо
Канал: @marg1nales Следящий: @CbEBITECb Папка: актив+рп пдп: 15:15 Допы: @nuar_melkor @Tommyangeles @drincell @Vkdrki0 @KimTlllll @YIN2O @Kastiel_Melkor @VA5G0D @aki_useful @YGB2O @BLABLABLALAAAAAAAAA @TIklIkx @vivivivizx @DEF_302
Канал: @frandeim Следящий: @BR_999al Папка: актив Подписка: 7:7 Допы: @shygadaddy @angllsky @fffrtttn @at55_fr @PDL2R @mdopppm 40 соо
Канал – @AN4K0ND Следящий – @HUMBERT010 Правила – @unionlistdas Папка – актив+рп. Подписка – 5:5. Допы: @IN3IT10N @DKNY010 @LGAURE @HE1SAR 40 соо
канал - @EVERSKIEZ след - @favourite_bear папка - актив+рп допы: @c3lest33 @Amalfi_Fallor @DOP4_EVERS @DOP5_EVERS @DOP6_EVERS @DOP_EVERS7 @DOP8_EVERS @DOP9_EVERS @DOP10_EVERS @DOP_EVERS11 @DOP12_EVERS @DOP13_EVERS @DOP14_EVERS @lilyshe 40 соо
канал: @GROMOVSK1E след: @DI0GBQ1 папка: актив пдп: @SKE7RT1 @GR1F701 @GR10ER @ARTiCN1 @CO10IR @quietdonte @LSTY0 @po_opik @zeenj_gr @vnn_nnnnn @ALMI1X @nyxik_e @ways1god @GNFTAS 30 соо ❌
@BERVSU — @Adenovskie_off 26.06-05.07 @gford76 — @DARKMARIS 27.06-20.07 @ck_swan — @neroxu @KRDMKL — @HMMLSK 24.06-29.06 @BERVSU — @muveszeeti 26.06-05.07 @nahyyyyyyy — @Street_dance_channel @liqdnt — @Eskortskie_chnl 11.06-07.07 @SRN8XS — @ONLFAMILYOU @SORTADLE — @chasovskieworld 22.06-03.07 @vkvirz — @HALOR1A 25.06-30.06 @adsonsimm — @detxdom 01.07-17.07 @BR0_0S — @SPUTION_FM 01.07-06.07 @mnkpaam — @luxarias122 22…
канал - @BRDG7R папка - актив + рп подписка - 10×10 следящий - @B5D4KL допы - @jwkcrypt @JK7S000 @coldhx @stxrsky7 @B5D7KL @durksgt @honshul @S7PHR1 @GT7HUB 40 соо
канал @mersedfml след @ST04M3 папки вз пдп 15:15 допы @shabrovarinelle @milki_cuteleo @shabrovari @e1leeng7 @sto12rmy @Jkminmi19 @sixseven67ahsex @QWXXR1 @taeudy @tuyves @bOyFUlL991XD @Makicatt @cessvel @Gmelllimll
Канал : @KINGDOM_KOGTAN Следящий : @S3R4R1 Личные правила! Папка : актив+рп пдп 6:6 допы @D7ZDR @SXXRRVV @Lacosteso @samuraihdg @KnFmn 40 соо
Showing the 12 most recent of 20 posts we hold for @tAEw11s. 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“пингвиний уголок” (@tAEw11s), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tAEw11s.
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.