Telegram RegisterThe public register of Telegram
Telegram profile photo for 淡い夏のWindows bugs

Channel

淡い夏のWindows bugs

@windows_bugs_by_awainatsu

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

44subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002048357732
TypeChannel
Username@windows_bugs_by_awainatsu
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live9 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/windows_bugs_by_awainatsu

Growth

434443.57 August 2026 — 43 subscribers10 August 2026 — 43 subscribers9 October 2026 — 44 subscribers7 August 20269 October 2026
3 measurements spanning 64 days, net +1. 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 43–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 15:1444+1
10 Aug 2026, 17:0143no change
7 Aug 2026, 03:0743first reading

Engagement

18 posts held, back to 16 November 2024 — 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 page 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 18 posts for this entry, the most recent from 13 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
30s
Average length
15s

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

21 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 38.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😇838.1%
🤯628.6%
😭419.0%
🥰29.52%
🤣14.76%

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

Measured over the 18 most recent posts we hold, published 16 November 2024 to 13 June 2025, 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

13 Jun 2025, 14:06 UTC241 viewsread 10 August 2026
Video

正 合 我 意 (猜测可能是因为我的电脑上没有Edge,不过你这个App的作用如果就只是打开Edge的话 那扬了也罢

Signed Il Harper

29 Mar 2025, 11:23 UTC332 views3 reactionsread 10 August 2026
Photo

这侧边栏什么似人边距

😇3

Signed 淡い夏

26 Feb 2025, 11:08 UTC320 viewsread 10 August 2026
Photo

奇怪地炸掉的样式,莫名的XP复古感 (左:炸掉的 右:正常情况的

Signed Il Harper

30 Jan 2025, 11:00 UTC311 views3 reactionsread 10 August 2026
Photo

错误! 无法播放测试音调。 by 声音(未响应) 注:IlHarper 投稿的所有 bug 都是正式版的

🤯3

Signed Il Harper

30 Jan 2025, 10:45 UTC237 views2 reactionsread 10 August 2026
Sticker

Sticker, posted without a caption

🥰2

Signed 淡い夏

30 Jan 2025, 10:13 UTC244 views4 reactionsread 10 August 2026

27783.1000 喜提资源管理器反复崩溃,安全引导无法还原此前版本,乐😇

😭4

11 Jan 2025, 07:37 UTC236 views4 reactionsread 10 August 2026
Photo

没修也就算了,左边又是怎么回事

😇4

10 Dec 2024, 04:42 UTC267 viewsread 10 August 2026
Photo

一张图两个 bug,真有微软的 爱来自(27758.1000)

9 Dec 2024, 11:47 UTC211 views1 reactionsread 10 August 2026
Photo

我什么时候组的 RAID 我自己怎么都不知道(

🤣1

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

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

“淡い夏のWindows bugs” (@windows_bugs_by_awainatsu), 44 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/windows_bugs_by_awainatsu.

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.