Telegram RegisterThe public register of Telegram
Telegram profile photo for ПЕРЕЕЗД

Channel

ПЕРЕЕЗД

@wyzhxi1997

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

3subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1001968413539
TypeChannel
Username@wyzhxi1997
Descriptionлюблю лизу . .
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/wyzhxi1997

Growth

313 Aug 2026, 09:31 — 3 subscribers13 Aug 2026, 18:36 — 3 subscribers13 Aug 2026, 09:3113 Aug 2026, 18:36
2 measurements taken within a single day. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 18:363no change
13 Aug 2026, 09:313first reading

Engagement

13 posts held, back to 19 December 2023the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 21 December 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1,280
Videos
50
Links
78

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

217 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54113120001206647936429.5%
custom 54223981868849714276027.6%
custom 54025650415243228885424.9%
custom 52695607534545910223918.0%

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

Measured over the 13 most recent posts we hold, published 19 December 2023 to 21 December 2023, 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

21 Dec 2023, 16:52 UTC252 viewsread 13 August 2026

я рестникам завтра напишу😴😴😴😴

21 Dec 2023, 16:52 UTC252 viewsread 13 August 2026

этот канал свое отслужил 💋 @wyzhxi1905

21 Dec 2023, 16:30 UTC247 views7 reactionsread 13 August 2026

- а может переезд . . 🌟

custom 54025650415243228886custom 52695607534545910221

21 Dec 2023, 15:16 UTC249 views19 reactionsread 13 August 2026
Photo

10 класс🤗🤗

custom 540256504152432288811custom 54223981868849714274custom 54113120001206647933custom 52695607534545910221

21 Dec 2023, 15:12 UTC242 views21 reactionsread 13 August 2026
Photo

решите мне кто-нибудь пожалуйста🤗

custom 54113120001206647939custom 54223981868849714279custom 54025650415243228882custom 52695607534545910221

20 Dec 2023, 16:11 UTC156 views36 reactionsread 13 August 2026

- я буквально пять часов подряд делала дз. и это только за завтра. сейчас у меня рука отвалится, а спина сломается. я так устала хелп😭 мне ещё английский повторять, мм кайф. сейчас буду отдыхать, наконец-то зато я так высплюсь сегодня💋 надеюсь, у вас все хорошо ! ! 💋

custom 541131200012066479314custom 542239818688497142711custom 526956075345459102210custom 54025650415243228881

19 Dec 2023, 15:14 UTC131 views32 reactionsread 13 August 2026

можно ли как-нибудь зарегаться в твиттер, если у меня российский номер? или у меня нет надежд? 😔

custom 542239818688497142710custom 54113120001206647938custom 52695607534545910227custom 54025650415243228887

19 Dec 2023, 10:30 UTC123 views49 reactionsread 13 August 2026
Photo

🤏🤏

custom 541131200012066479317custom 540256504152432288814custom 542239818688497142714custom 52695607534545910224

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

Citation-graph rank

Citation-graph rank — 624,178 of 1,481,277entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“ПЕРЕЕЗД” (@wyzhxi1997), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/wyzhxi1997.

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.