Telegram RegisterThe public register of Telegram
Telegram profile photo for Ami’

Channel

Ami’

@amipevec61

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

103subscribers

-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-1003648400382
TypeChannel
Username@amipevec61
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live12 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/amipevec61

Topic

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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.

Growth

1021121077 August 2026 — 104 subscribers9 August 2026 — 104 subscribers16 August 2026 — 105 subscribers24 August 2026 — 102 subscribers1 September 2026 — 106 subscribers10 September 2026 — 109 subscribers18 September 2026 — 112 subscribers2 October 2026 — 105 subscribers12 October 2026 — 103 subscribers1037 August 202612 October 2026
9 measurements spanning 66 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 101–114 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 20:36103-2
2 Oct 2026, 21:15105-7
18 Sept 2026, 06:20112+3
10 Sept 2026, 16:36109+3
1 Sept 2026, 08:06106+4
24 Aug 2026, 17:06102-3
16 Aug 2026, 20:16105+1
9 Aug 2026, 09:17104no change
7 Aug 2026, 19:40104first reading

Engagement

13 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 13 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
23s
Average length
6s

Measured directly from 4 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

593 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 33.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤19933.6%
🔥10718.0%
custom 54587836981177430067713.0%
🥰6611.1%
custom 5210730451802544865305.06%
custom 5461066739523544307305.06%
custom 5355248808458472870244.05%
custom 5454357876053138877244.05%
custom 5355134394824674953203.37%
custom 5454087950243489905162.70%

Custom emoji. 7 of the rows above are 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 13 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 593 reactions 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 30 July 2026 to 8 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.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
3
of 13 we hold a reading for · 23%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @amipevec61. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 13 most recent posts we hold for this entry, published 30 July 2026 to 8 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

8 Aug 2026, 16:34 UTC44 views13 reactions1 Starread 9 August 2026
Photo

Улетаю на Гаити

custom 54587836981177430068custom 53552488084584728705

7 Aug 2026, 09:32 UTC65 views25 reactionsread 9 August 2026
Photo

Опять он в горах

❤10custom 53551343948246749536custom 54587836981177430066custom 53552488084584728703

6 Aug 2026, 02:07 UTC78 views30 reactionsread 9 August 2026
Video message

Video message, posted without a caption

❤8custom 54587836981177430066custom 54610667395235443076custom 53551343948246749535custom 54543578760531388775

5 Aug 2026, 18:16 UTC93 views42 reactionsread 9 August 2026
Photo

Спонсор сегодняшнего вечера 🚗

❤12🔥6custom 53552488084584728706custom 54540879502434899055custom 54587836981177430065custom 52107304518025448654custom 54610667395235443074

4 Aug 2026, 14:49 UTC107 views44 reactionsread 9 August 2026

Возвращаю эру пианино

❤14custom 545878369811774300610🔥8custom 54540879502434899056custom 54543578760531388776

4 Aug 2026, 14:49 UTC109 views43 reactionsread 9 August 2026
Voice message

Voice message, posted without a caption

custom 545435787605313887713custom 54587836981177430068❤5custom 53552488084584728705🔥4custom 52107304518025448654custom 54610667395235443074

1 Aug 2026, 17:33 UTC149 views74 reactionsread 9 August 2026
Photo

Я снова лучше чем твой бывший 💋

❤24custom 545878369811774300620🔥16custom 53552488084584728705custom 54540879502434899055custom 52107304518025448654

31 Jul 2026, 18:48 UTC138 views68 reactions2 Starsread 9 August 2026
Video

Video, posted without a caption

❤26🔥21🥰21

31 Jul 2026, 18:37 UTC127 views55 reactionsread 9 August 2026
Photo

🇬🇪🇬🇪🇬🇪

❤21custom 521073045180254486518🔥16

31 Jul 2026, 18:14 UTC126 views52 reactionsread 9 August 2026
Video message

Video message, posted without a caption

❤23🥰15🔥14

31 Jul 2026, 17:32 UTC120 views51 reactionsread 9 August 2026
Video

Video, posted without a caption

❤20🔥16🥰15

31 Jul 2026, 16:54 UTC126 views50 reactionsread 9 August 2026
Video message

Video message, posted without a caption

❤19custom 546106673952354430716🥰15

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“Ami’” (@amipevec61), 103 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/amipevec61.

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.