21 Aug 2026, 16:35 UTC52 viewsread 1 September 2026
Photo
Анастасия К 89/61/92, 174 Booking @amimodelsscout
Channel
AMI MODELS MANAGEMENT
@amimodelsmanagement
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
102subscribers
-2 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002551165862 |
|---|---|
| Type | Channel |
| Username | @amimodelsmanagement |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/amimodelsmanagement |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 10:21 | 102 | -2 |
| 1 Sept 2026, 11:45 | 104 | no change |
| 1 Sept 2026, 11:31 | 104 | first reading |
Engagement
6 posts held, back to 30 June 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 6 posts for this entry, the most recent from 21 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 5s
- Average length
- 5s
Measured directly from 1 video 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.
Recent posts
21 Aug 2026, 16:29 UTC55 viewsread 1 September 2026
Photo
New model Илья Рост 186 Booking @amimodelsscout
24 Jul 2026, 12:00 UTC117 viewsread 1 September 2026
Photo
Вooking Съемка для рекламы «аренды одежды» Anna 169 85/66/98 Booking @amimodelsscout
2 Jul 2026, 20:06 UTC180 viewsread 1 September 2026
Photo
Екатерина Ф 160 85/64/90 Booking @amimodelsscout
1 Jul 2026, 11:52 UTC161 viewsread 1 September 2026
Photo
Beauty Анастасия В 178 85/68/100 Booking @amimodelsscout
30 Jun 2026, 13:59 UTC142 viewsread 1 September 2026
Photo
Матвей М CATALOG 178 88/74/90 Booking @amimodelsscout
Showing the 6 most recent of 6 posts we hold for @amimodelsmanagement. 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
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“AMI MODELS MANAGEMENT” (@amimodelsmanagement), 102 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/amimodelsmanagement.
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.