Telegram RegisterThe public register of Telegram
Telegram profile photo for WALLPAPERS RANDOM

Channel

WALLPAPERS RANDOM

@WallpapersRandom

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

16,727subscribers

-258 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001359694186
TypeChannel
Username@WallpapersRandom
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/WallpapersRandom

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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.

Growth

16,72716,98516,8566 August 2026 — 16,985 subscribers7 August 2026 — 16,977 subscribers8 August 2026 — 16,971 subscribers9 August 2026 — 16,961 subscribers10 August 2026 — 16,959 subscribers11 August 2026 — 16,943 subscribers12 August 2026 — 16,932 subscribers13 August 2026 — 16,925 subscribers14 August 2026 — 16,906 subscribers16 August 2026 — 16,892 subscribers17 August 2026 — 16,889 subscribers18 August 2026 — 16,888 subscribers20 August 2026 — 16,875 subscribers21 August 2026 — 16,871 subscribers23 August 2026 — 16,857 subscribers24 August 2026 — 16,846 subscribers25 August 2026 — 16,843 subscribers27 August 2026 — 16,832 subscribers27 August 2026 — 16,831 subscribers29 August 2026 — 16,820 subscribers29 August 2026 — 16,827 subscribers31 August 2026 — 16,816 subscribers1 September 2026 — 16,806 subscribers2 September 2026 — 16,803 subscribers3 September 2026 — 16,795 subscribers5 September 2026 — 16,793 subscribers8 September 2026 — 16,773 subscribers11 September 2026 — 16,752 subscribers13 September 2026 — 16,746 subscribers15 September 2026 — 16,744 subscribers17 September 2026 — 16,727 subscribers6 August 202617 September 2026
31 measurements spanning 42 days, net -258. 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 16,688–17,024 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
17 Sept 2026, 04:2116,727-17
15 Sept 2026, 01:5816,744-2
13 Sept 2026, 07:5816,746-6
11 Sept 2026, 12:1916,752-21
8 Sept 2026, 22:3616,773-20
5 Sept 2026, 12:5816,793-2
3 Sept 2026, 17:1716,795-8
2 Sept 2026, 06:4416,803-3
1 Sept 2026, 05:0716,806-10
31 Aug 2026, 01:3816,816-11
29 Aug 2026, 22:0416,827+7
29 Aug 2026, 00:5816,820-11
27 Aug 2026, 21:5316,831-1
27 Aug 2026, 00:5316,832-11
25 Aug 2026, 22:2416,843-3
24 Aug 2026, 19:3716,846-11
23 Aug 2026, 03:1316,857-14
21 Aug 2026, 13:0816,871-4
20 Aug 2026, 11:0616,875-13
18 Aug 2026, 11:0316,888first reading

Engagement

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

ERR · 30 days
4.30%
avg views ÷ 16,727 subscribers
Avg views / post
719
34 posts measured
Reaction rate
0.65%
reactions ÷ views · ER floor
Posts in window
34
of 75 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. It is computed over the 18 of 34 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held75 (25 July 20263 September 2026)
Views total24,448
Reactions total109
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 09:37 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.

Reaction mix

317 reactions across 49 posts, in 2 distinct kinds. The most used accounts for 85.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍27185.5%
👏4614.5%

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

Measured over the 75 most recent posts we hold, published 25 July 2026 to 3 September 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

3 Sept 2026, 02:00 UTC136 viewsread 3 September 2026
Photo

[🚨¿LISTO PARA DESCUBRIR LO QUE TE ESPERA?🚨] 🔥 ¡No puedes dejar pasar esto! Hemos reunido los canales más exclusivo a los que puedes unirte HOY MISMO. 🌟 ➕ ¿Quieres añadir tu canal? ℹ️: https://t.me/+dWtXBpH90IgyNzEx 🤖: @MegaBotonera_Valkyria02_Pro_bot

2 Sept 2026, 02:04 UTC47 viewsread 2 September 2026
Photo

[🚨¿LISTO PARA DESCUBRIR LO QUE TE ESPERA?🚨] 🔥 ¡No puedes dejar pasar esto! Hemos reunido los canales más exclusivo a los que puedes unirte HOY MISMO. 🌟 ➕ ¿Quieres añadir tu canal? ℹ️: https://t.me/+dWtXBpH90IgyNzEx 🤖: @MegaBotonera_Valkyria02_Pro_bot

31 Aug 2026, 23:31 UTC614 viewsread 3 September 2026
File

🆕 Nuevo Wallpaper ⭐️ Canal ➜ WallpapersRandom •• ━━━━ ••●•• ━━━━ •• 💭 Únete a Nuestra Comunidad ➜ Nuestros Canales 👨‍🔧 Soporte por chat / Atención ➜ @CommunityManagerADM_Bot •• ━━━━ ••●•• ━━━━ •• Apoya el Contenido 🌟 📥 🔂 ˡᶦᵏᵉ ˢᵃᵛᵉ ˢʰᵃʳᵉ

31 Aug 2026, 23:31 UTC586 views5 reactionsread 3 September 2026
Photo

🆕 Nuevo Wallpaper ⭐️ Canal ➜ WallpapersRandom •• ━━━━ ••●•• ━━━━ •• 💭 Únete a Nuestra Comunidad ➜ Nuestros Canales 👨‍🔧 Soporte por chat / Atención ➜ @CommunityManagerADM_Bot •• ━━━━ ••●•• ━━━━ •• Apoya el Contenido 🌟 📥 🔂 ˡᶦᵏᵉ ˢᵃᵛᵉ ˢʰᵃʳᵉ

👍5

31 Aug 2026, 19:30 UTC552 views7 reactionsread 3 September 2026
Photo

🆕 Nuevo Wallpaper ⭐️ Canal ➜ WallpapersRandom •• ━━━━ ••●•• ━━━━ •• 💭 Únete a Nuestra Comunidad ➜ Nuestros Canales 👨‍🔧 Soporte por chat / Atención ➜ @CommunityManagerADM_Bot •• ━━━━ ••●•• ━━━━ •• Apoya el Contenido 🌟 📥 🔂 ˡᶦᵏᵉ ˢᵃᵛᵉ ˢʰᵃʳᵉ

👍7

31 Aug 2026, 19:30 UTC561 viewsread 3 September 2026
File

🆕 Nuevo Wallpaper ⭐️ Canal ➜ WallpapersRandom •• ━━━━ ••●•• ━━━━ •• 💭 Únete a Nuestra Comunidad ➜ Nuestros Canales 👨‍🔧 Soporte por chat / Atención ➜ @CommunityManagerADM_Bot •• ━━━━ ••●•• ━━━━ •• Apoya el Contenido 🌟 📥 🔂 ˡᶦᵏᵉ ˢᵃᵛᵉ ˢʰᵃʳᵉ

31 Aug 2026, 17:27 UTC527 views1 reactionsread 3 September 2026

Para seguir creciendo juntos y traerles siempre el mejor contenido, no olviden dejar su reaction/like (👍) en las publicaciones. Cada interacción de ustedes nos motiva a seguir compartiendo lo mejor. ​¡A romperla esta semana! 💪🔥

👍1

31 Aug 2026, 15:32 UTC559 viewsread 3 September 2026
File

🆕 Nuevo Wallpaper ⭐️ Canal ➜ WallpapersRandom •• ━━━━ ••●•• ━━━━ •• 💭 Únete a Nuestra Comunidad ➜ Nuestros Canales 👨‍🔧 Soporte por chat / Atención ➜ @CommunityManagerADM_Bot •• ━━━━ ••●•• ━━━━ •• Apoya el Contenido 🌟 📥 🔂 ˡᶦᵏᵉ ˢᵃᵛᵉ ˢʰᵃʳᵉ

31 Aug 2026, 15:32 UTC584 views6 reactionsread 3 September 2026
Photo

🆕 Nuevo Wallpaper ⭐️ Canal ➜ WallpapersRandom •• ━━━━ ••●•• ━━━━ •• 💭 Únete a Nuestra Comunidad ➜ Nuestros Canales 👨‍🔧 Soporte por chat / Atención ➜ @CommunityManagerADM_Bot •• ━━━━ ••●•• ━━━━ •• Apoya el Contenido 🌟 📥 🔂 ˡᶦᵏᵉ ˢᵃᵛᵉ ˢʰᵃʳᵉ

👍6

31 Aug 2026, 02:01 UTC60 viewsread 31 August 2026
Photo

[🚨¿LISTO PARA DESCUBRIR LO QUE TE ESPERA?🚨] 🔥 ¡No puedes dejar pasar esto! Hemos reunido los canales más exclusivo a los que puedes unirte HOY MISMO. 🌟 ➕ ¿Quieres añadir tu canal? ℹ️: https://t.me/+dWtXBpH90IgyNzEx 🤖: @MegaBotonera_Valkyria02_Pro_bot

30 Aug 2026, 02:02 UTC36 viewsread 30 August 2026
Photo

[🚨¿LISTO PARA DESCUBRIR LO QUE TE ESPERA?🚨] 🔥 ¡No puedes dejar pasar esto! Hemos reunido los canales más exclusivo a los que puedes unirte HOY MISMO. 🌟 ➕ ¿Quieres añadir tu canal? ℹ️: https://t.me/+dWtXBpH90IgyNzEx 🤖: @MegaBotonera_Valkyria02_Pro_bot

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

Mentions

Named by 3 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

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.

TEMAS TGM
@TemasTGM · 26,209
Telegram ranks this channel #2 of 56 here — alongside 55 others — read 12 September 2026
MUNDO FITNESS🏋🏻‍♂️💪
@Mundo_Fitness · 23,362
Telegram ranks this channel #50 of 63 here — alongside 62 others — read 18 September 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“WALLPAPERS RANDOM” (@WallpapersRandom), 16,727 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/WallpapersRandom.

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.