Telegram RegisterThe public register of Telegram
Telegram profile photo for ОТЗЫВЫ о работе с Arch1k3

Channel

ОТЗЫВЫ о работе с Arch1k3

@otziviarch1k3

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

10subscribers

+2 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-1001695820500
TypeChannel
Username@otziviarch1k3
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live8 October 2026
Measurements held4
Confirmed unchanged5 times, most recently 8 October 2026
On Telegramt.me/otziviarch1k3

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 2 October 2026 and assigned it the closest of 31 fixed categories, at 69% 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

81097 August 2026 — 8 subscribers12 August 2026 — 8 subscribers15 August 2026 — 9 subscribers28 August 2026 — 10 subscribers7 August 202628 August 2026
4 measurements spanning 21 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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 14:1710+1
15 Aug 2026, 05:579+1
12 Aug 2026, 14:318no change
7 Aug 2026, 18:458first reading

Engagement

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

Recent posts

7 Aug 2026, 14:25 UTC24 viewsread 12 August 2026
Photo

@Arch1k3 закрыл реку, забрал на покушать, все супер

31 Jul 2026, 10:50 UTC44 viewsread 12 August 2026

@Arch1k3 арчик братан как всегда все сделал просто на высшем уровне. безумно приятно работать, и посоветоваться можно, и компромиссы нашли, и воркаем быстро. крч мужик настоящий

29 Jul 2026, 13:12 UTC53 viewsread 12 August 2026
Photo

@Arch1k3 лучший тип , закриває рекламу уже не первий раз , РЕКОМЕНДУЮ НАХУЙ 🤫

8 Jul 2026, 16:14 UTC109 viewsread 12 August 2026

@Arch1k3 заебись типок люблю его все четко и по госту делает продал реку и купил футболку Армани

3 Jul 2026, 18:43 UTC114 viewsread 12 August 2026

@Arch1k3 лучший рек менеджер заплатил всё вовремя советую к сотрудничеству

3 Jul 2026, 14:31 UTC111 viewsread 12 August 2026
Photo

Красавчик @Arch1k3 Закрыл рекламу по пдп, в гарант зашло, кэш пришел , все топ огонь пулемет 🔥

3 Jul 2026, 10:04 UTC97 viewsread 12 August 2026
Photo

@Arch1k3 закрыл фаст рекламу без срезов оперативно! Рекомендую

20 Jun 2026, 11:49 UTC131 viewsread 12 August 2026
Photo

@Arch1k3 норм товарищ закрывает реку как бог, максимально трастовый чел, всем советую

13 Jun 2026, 20:41 UTC140 viewsread 12 August 2026

@Arch1k3 Закрыл рекламу трейда по гаранту, с оплатой не подвел все четко

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

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

“ОТЗЫВЫ о работе с Arch1k3” (@otziviarch1k3), 10 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/otziviarch1k3.

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.