Telegram RegisterThe public register of Telegram

Channel

pnvm / any cross

@anycross

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

1,027subscribers

-2 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001307544531
TypeChannel
Username@anycross
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/anycross

Growth

1,0271,0291,0289 August 2026 — 1,029 subscribers9 August 2026 — 1,029 subscribers12 August 2026 — 1,027 subscribers9 August 202612 August 2026
3 measurements spanning 3 days, net -2. 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 1,027–1,029 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 09:391,027-2
9 Aug 2026, 18:121,029no change
9 Aug 2026, 12:161,029first reading

Engagement

18 posts held, back to 1 April 2026the 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 18 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

220 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 35.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53549331283622348007735.0%
custom 52786330085789615407433.6%
custom 53395424308845857313616.4%
custom 53234353457468623033315.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 18 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 220reactions 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 1 April 2026 to 3 July 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

3 Jul 2026, 07:15 UTC432 views14 reactionsread 9 August 2026

omanko day 2 — круто ! друзья — спасибо всем кто пришел и поддержал наш "мультикорнер"

custom 527863300857896154011custom 53549331283622348002custom 53234353457468623031

22 Jun 2026, 13:17 UTC822 views7 reactionsread 9 August 2026
Photo

27-28 июня буду на ÖMANKÖ DAY будут сережки + презентую новое кольцо , которое будет доступно для пред заказа возможно футболки доделаю .. но это не точно буду рад видеть каждого!

custom 52786330085789615407

3 Jun 2026, 13:08 UTC876 views7 reactionsread 9 August 2026
Location

Location, posted without a caption

custom 53549331283622348004custom 53234353457468623032custom 52786330085789615401

3 Jun 2026, 13:08 UTC817 views32 reactionsread 9 August 2026
Photo

все : на японию обрушился сильный тайфун 🌪️🌧️ тем временем я :

custom 533954243088458573117custom 527863300857896154010custom 53234353457468623033custom 53549331283622348002

15 May 2026, 15:04 UTC≈1,010 views8 reactionsread 9 August 2026

🛵 Москва — в IF на выходных и раздаем карточки 🪪

custom 53549331283622348007custom 53395424308845857311

15 May 2026, 15:01 UTC960 views10 reactionsread 9 August 2026

ᴙИᗆ∀Ԁ⊥Ɔᗺ∀

custom 53395424308845857318custom 52786330085789615401custom 53234353457468623031

15 May 2026, 08:56 UTC974 views5 reactionsread 9 August 2026
Sticker

Sticker, posted without a caption

custom 53549331283622348005

15 May 2026, 08:55 UTC926 views13 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 53549331283622348009custom 52786330085789615404

8 May 2026, 18:23 UTC≈1,120 views14 reactionsread 9 August 2026
Photo

🙏

custom 533954243088458573110custom 52786330085789615404

1 May 2026, 07:53 UTC≈1,220 views16 reactionsread 9 August 2026
Video

👤 Мой ID — подробнее о solu.ID

custom 535493312836223480016

23 Apr 2026, 14:48 UTC≈1,230 views13 reactionsread 9 August 2026

кто пойдет на оманко дей в этом году ?

custom 532343534574686230313

Showing the 12 most recent of 18 posts we hold for @anycross. 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 — 1,120,348 of 1,160,990entries 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.

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

“pnvm / any cross” (@anycross), 1,027 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/anycross.

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.