📍Fujikawaguchiko, 富士河口湖
custom 526071893191558586216custom 52606484772720629227custom 52629821992919537266

Channel
@wixlef
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
690subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001673451277 |
|---|---|
| Type | Channel |
| Username | @wixlef |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/wixlef |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 |
|---|---|---|
| 2 Oct 2026, 19:01 | 690 | -3 |
| 17 Sept 2026, 23:59 | 693 | -3 |
| 9 Sept 2026, 00:00 | 696 | -3 |
| 30 Aug 2026, 20:28 | 699 | -2 |
| 23 Aug 2026, 05:02 | 701 | +7 |
| 15 Aug 2026, 07:22 | 694 | +2 |
| 8 Aug 2026, 02:20 | 692 | no change |
| 7 Aug 2026, 13:07 | 692 | first reading |
7 posts held, back to 30 July 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 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 7 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
239 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 42.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5262982199291953726 | 101 | 42.3% | |
| custom 5260718931915585862 | 75 | 31.4% | |
| custom 5260648477272062922 | 63 | 26.4% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 7 of the 7 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 239 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 30 July 2026 to 3 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.
📍Fujikawaguchiko, 富士河口湖
custom 526071893191558586216custom 52606484772720629227custom 52629821992919537266
проснулась вот с таким видом, а у вас как дела? (это фудзи сори моя удача как всегда)
custom 526298219929195372621custom 52606484772720629229custom 52607189319155858626
пройдут года и я перестану скупать всякую милую фигню, но явно не сегодня… 🤪
custom 526298219929195372617custom 52606484772720629227custom 52607189319155858625
osaka p.2
custom 526064847727206292217custom 52629821992919537265custom 52607189319155858624
🦋
custom 526071893191558586223custom 52606484772720629227custom 52629821992919537266
some osaka vibe вам в ленту
custom 526298219929195372621custom 526071893191558586210custom 52606484772720629228
📍 Nijō Castle, Kyoto 京都
custom 526298219929195372625custom 526071893191558586211custom 52606484772720629228
Showing the 7 most recent of 7 posts we hold for @wixlef. 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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“wixlef” (@wixlef), 690 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/wixlef.
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.