Telegram RegisterThe public register of Telegram
Telegram profile photo for Nagasaki Stuff

Channel

Nagasaki Stuff

@NagasakiStuff

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

49subscribers

+27 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004456701015
TypeChannel
Username@NagasakiStuff
Created7 August 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live13 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/NagasakiStuff

Previous handles

@NagasakiStuff was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@NaomiWallsUpdates
held 11 August 202611 August 2026

Growth

224935.59 August 2026 — 22 subscribers9 August 2026 — 24 subscribers11 August 2026 — 24 subscribers27 August 2026 — 40 subscribers28 August 2026 — 41 subscribers6 September 2026 — 46 subscribers13 September 2026 — 49 subscribers9 August 202613 September 2026
7 measurements spanning 35 days, net +27. 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 18–53 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 11:3649+3
6 Sept 2026, 00:2046+5
28 Aug 2026, 05:5641+1
27 Aug 2026, 13:0040+16
11 Aug 2026, 10:1824no change
9 Aug 2026, 19:5224+2
9 Aug 2026, 14:1522first reading

Engagement

22 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
128.6%
avg views ÷ 49 subscribers
Avg views / post
63.0
4 posts measured
Reaction rate
2.07%
reactions ÷ views · ER floor
Posts in window
4
of 22 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 1 of 4 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 26 August 2026
Posts held22 (7 August 202626 August 2026)
Views total252
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Aug 2026, 13:00 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

15 reactions across 6 posts, in 10 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
320.0%
😁320.0%
😢213.3%
🎉16.67%
🏆16.67%
👍16.67%
👏16.67%
🔥16.67%
🙏16.67%
🥰16.67%

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

Measured over the 22 most recent posts we hold, published 7 August 2026 to 26 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

26 Aug 2026, 23:50 UTC145 views3 reactionsread 27 August 2026
Photo

#ROM #ProjectSakura #Unofficial #Ginkllow #Aosp #Baklava Project Sakura 16.3.0 Android 16 | QPR2 Released: 27/08/'26 ▪️Download ▪️Join Channel ▪️Support Group ▪️Screenshot ▪️Credits Notes • Vanilla Rom • Clean Flash Recommended • Non Dynamic Rom • Use Nikgapps A16 QPR2  By @MrJuanNagasaki Follow @NagasakiStuff Join @NagasakiSupport

1🎉1👏1

Signed Nāgasaki Jūan ("⁧;("

26 Aug 2026, 23:45 UTC26 viewsread 27 August 2026
Forwarded from @WisteriaWallsPhoto

Cloudy Nap Wallpaper 🎉 Thanks MySelf For Wallpaper Get it Join @WisteriaWalls Follow @WisteriaDiscussion By @Kartikay_12

Signed Nāgasaki Jūan ("⁧;("

23 Aug 2026, 20:01 UTC45 viewsread 27 August 2026
Forwarded from @undyingwallsPhoto

New waguri wallpaper 😁❤️ Hope y'all like Get it THANKS TO @eepywolly for the banner For a special friend hehe By @@sl1txxz Join @undyingschat Follow @undyingwalls

Signed Nāgasaki Jūan ("⁧;("

23 Aug 2026, 13:26 UTC36 viewsread 27 August 2026
Forwarded from @WisteriaWallsPhoto

Yellow duck Wallpaper 🎉 Thanks MySelf For Wallpaper Thanks @MrJuanNagasaki for Banner Get it Join @WisteriaWalls Follow @WisteriaDiscussion By @Kartikay_12

Signed Nāgasaki Jūan ("⁧;("

20 Aug 2026, 16:04 UTC35 viewsread 27 August 2026
Forwarded from @WisteriaWallsPhoto

Obani Iguro Wallpaper 💜 Thanks MySelf For Wallpaper and Banner Get it Join @WisteriaWalls Follow @WisteriaDiscussion By @MrJuanNagasaki

Signed Nāgasaki Jūan ("⁧;("

20 Aug 2026, 14:42 UTC33 viewsread 27 August 2026
Forwarded from @WisteriaWallsPhoto

Crimson Roar Wallpaper 🎉 Thanks MySelf For Wallpaper and Banner Get it Join @WisteriaWalls Follow @WisteriaDiscussion By @Kartikay_12

Signed Nāgasaki Jūan ("⁧;("

17 Aug 2026, 14:57 UTC44 viewsread 27 August 2026
Forwarded from @WisteriaWallsPhoto

Autumn Veil Wallpaper 🥳 Thanks MySelf For Wallpaper and Banner Get it Join @WisteriaWalls Follow @WisteriaDiscussion By @Kartikay_12

Signed Nāgasaki Jūan ("⁧;("

15 Aug 2026, 07:41 UTC38 viewsread 27 August 2026
Forwarded from @undyingwallsPhoto

Zenitsu Agatsuma Wallpaper 🎐 Get it Thanks @MrJuanNagasaki For Banner Hope y'all Like It 🥰 Join @undyingschat Follow @undyingwalls By @MrJuanNagasaki

Signed Nāgasaki Jūan ("⁧;("

14 Aug 2026, 19:10 UTC100 viewsread 27 August 2026
File

File, posted without a caption

Signed Nāgasaki Jūan ("⁧;("

14 Aug 2026, 19:09 UTC103 viewsread 27 August 2026
Photo

Happy 80th Independence Day 🇮🇳 Warm wishes are Extended From Japan. There is a sense of pride in the nation's progress and gratitude for the freedom celebrated today Jai Hind ! Jai Bharat ! — Nagasaki Juan

Signed Nāgasaki Jūan ("⁧;("

14 Aug 2026, 13:33 UTC30 viewsread 27 August 2026
Forwarded from @WisteriaWallsPhoto

Golden Bloom Wallpaper 🥨 Thanks MySelf For Wallpaper and Banner Get it Join @WisteriaWalls Follow @WisteriaDiscussion By @Kartikay_12

Signed Nāgasaki Jūan ("⁧;("

14 Aug 2026, 11:22 UTC93 viewsread 27 August 2026
Photo

🎐 Some Screenshots From Xiaomi HyperOS 4 Do you Like The New Glass UI Trend? Well, Bad – it’s The New Design Language For HyperOS 4 The System Will Even Put Effort Into Rendering Realistic-Looking Refraction The redesigned UI will offer more customization options for the lock screen, letting you arrange the clock and notifications as you see fit. It will also let you resize folders and group widgets. Additionally,

Signed Nāgasaki Jūan ("⁧;("

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

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.

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

“Nagasaki Stuff” (@NagasakiStuff), 49 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/NagasakiStuff.

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.