Telegram RegisterThe public register of Telegram
Telegram profile photo for ПЕРЕХОД || 𝑨𝑳𝒀𝑨𝑺𝑲𝑨 𝑻𝑽𝑨𝑹𝑬𝑽𝑨#𝑹𝑶𝑳𝑬𝑽𝑰𝑲#𝑩𝑼𝑺𝒀

Channel

ПЕРЕХОД || 𝑨𝑳𝒀𝑨𝑺𝑲𝑨 𝑻𝑽𝑨𝑹𝑬𝑽𝑨#𝑹𝑶𝑳𝑬𝑽𝑰𝑲#𝑩𝑼𝑺𝒀

@eni_wiks

On this record: Growth · Engagement · Posts · Citations · Cite this entry

128subscribers

-6 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002575552900
TypeChannel
Username@eni_wiks
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live18 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/eni_wiks

Growth

12813413115 August 2026 — 134 subscribers16 August 2026 — 134 subscribers31 August 2026 — 133 subscribers10 September 2026 — 131 subscribers18 September 2026 — 128 subscribers15 August 202618 September 2026
5 measurements spanning 34 days, net -6. 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 127–135 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 00:41128-3
10 Sept 2026, 04:21131-2
31 Aug 2026, 19:34133-1
16 Aug 2026, 04:03134no change
15 Aug 2026, 03:15134first reading

Engagement

20 posts held, back to 22 September 2025the 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 20 posts for this entry, the most recent from 24 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Dec 2025, 21:07 UTC256 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

10 Dec 2025, 22:16 UTC265 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

30 Nov 2025, 13:06 UTC206 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

30 Nov 2025, 13:06 UTC157 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

11 Oct 2025, 18:04 UTC244 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

11 Oct 2025, 18:04 UTC215 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

11 Oct 2025, 18:04 UTC146 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

11 Oct 2025, 18:04 UTC131 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

11 Oct 2025, 18:04 UTC122 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

1 Oct 2025, 06:15 UTC161 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

1 Oct 2025, 06:15 UTC143 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

1 Oct 2025, 06:15 UTC108 viewsread 15 August 2026

ПЕРЕХОД https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr https://t.me/alyaska_tvr

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

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

“ПЕРЕХОД || 𝑨𝑳𝒀𝑨𝑺𝑲𝑨 𝑻𝑽𝑨𝑹𝑬𝑽𝑨#𝑹𝑶𝑳𝑬𝑽𝑰𝑲#𝑩𝑼𝑺𝒀” (@eni_wiks), 128 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/eni_wiks.

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.