23 Aug 2021, 13:27 UTC323 viewsread 12 August 2026
Обратился к @prometheus_service за услугой, результат получен на следующий день, в рамках оговоренный сроков, заказ сделан с очень большой скидкой, сервис на высоте, спасибо
Channel
Прометей Отзывы🗣
@prometheus_comment
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001369483629 |
|---|---|
| Type | Channel |
| Username | @prometheus_comment |
| Created | Between 1 April 2018 and 11 September 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/prometheus_comment |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:01 | 10 | no change |
| 6 Aug 2026, 18:08 | 10 | first reading |
Engagement
20 posts held, back to 11 September 2019 — 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 23 August 2021. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
31 May 2021, 18:24 UTC371 viewsread 12 August 2026
Огромное спасибо за помощь, дали советы, подсказали что делать, быстро ответили на вопросы и озвучили чёткие цены за услуги)
1 Feb 2021, 10:31 UTC486 viewsread 12 August 2026
привет! я хотел спросить можно я сделку через гарант сервис Midas bot создам символическую на 500 руб с вами? я ее сам все оплачу, просто хочу чтобы после нашей основной сделки с прошлой недели мы оба рейтинг заработали в Midas боте. Я остался доволен вашим сервисом и хотел бы как покупатель рейтинг получить
28 Oct 2020, 09:26 UTC594 viewsread 12 August 2026
Отличный сервис,все сделали меньше чем за час,обращусь не раз спасибо.
29 Jul 2020, 21:04 UTC563 viewsread 12 August 2026
Доволен сервисом совету
29 Jul 2020, 21:04 UTC597 viewsread 12 August 2026
Друзьям
29 Jul 2020, 21:04 UTC536 viewsread 12 August 2026
Воспользовался услугами данного сервиса. Предоплату скинул сразу без раздумий по скольку был насышен. Через пару часов поступило уведомление о том что работа сделана.
15 Jul 2020, 13:20 UTC502 viewsread 12 August 2026
Хороший гарант/Абитражник. Хорошо провёл обитраж. ❤️❤️💕💕💕
3 Jul 2020, 09:57 UTC476 viewsread 12 August 2026
Ребята @prometheus_service отлично справились с задачей. Работают оперативно, подскажут без проблем. Спасибо за работу, Рекомендую!!
30 May 2020, 12:55 UTC502 viewsread 12 August 2026
Отзыв: Обращаюсь не первый раз, поставленные задачи решаются всегда оперативно и качественно, да и ценник адекватный. Всем рекомендую!
23 Apr 2020, 17:52 UTC493 viewsread 12 August 2026
Большое спасибо @prometheus_service за оперативную помощь в поисках нужной информации, а также за приятные бонусы! Поразила оперативность. Ранее обращался к его коллегам и на такой же запрос уходило намного больше времени. 100% уверен, что не последний раз обращаюсь! 👍
19 Mar 2020, 17:21 UTC468 viewsread 12 August 2026
Неоднократно обращался к @prometheus_service по вопросам различной сложности: от пробива номера до работ с Юр лицами. Все четко и в срок, респект от фруктового сервиса 👍🤝
Showing the 12 most recent of 20 posts we hold for @prometheus_comment. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Прометей Отзывы🗣” (@prometheus_comment), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/prometheus_comment.
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.