Telegram RegisterThe public register of Telegram
Telegram profile photo for ОТЗОВИК WILDBERRIES | КАТАЛОГ | КУПЛЮ | БАРТЕР

Supergroup

ОТЗОВИК WILDBERRIES | КАТАЛОГ | КУПЛЮ | БАРТЕР

@OtzovikWildberries

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

25,195members

-386 since we began measuring on 7 August 2026

448 online right now

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001512404302
TypeSupergroup
Username@OtzovikWildberries
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/OtzovikWildberries

Topic

Ecommerce storefront — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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

25,19525,66925,4327 August 2026 — 25,581 members7 August 2026 — 25,578 members8 August 2026 — 25,570 members9 August 2026 — 25,549 members10 August 2026 — 25,536 members11 August 2026 — 25,523 members12 August 2026 — 25,514 members13 August 2026 — 25,497 members14 August 2026 — 25,669 members15 August 2026 — 25,669 members16 August 2026 — 25,653 members17 August 2026 — 25,636 members18 August 2026 — 25,622 members19 August 2026 — 25,603 members20 August 2026 — 25,586 members22 August 2026 — 25,569 members23 August 2026 — 25,550 members24 August 2026 — 25,527 members25 August 2026 — 25,507 members26 August 2026 — 25,498 members27 August 2026 — 25,470 members29 August 2026 — 25,452 members29 August 2026 — 25,441 members31 August 2026 — 25,432 members1 September 2026 — 25,417 members1 September 2026 — 25,406 members3 September 2026 — 25,392 members4 September 2026 — 25,366 members7 September 2026 — 25,332 members10 September 2026 — 25,293 members12 September 2026 — 25,265 members14 September 2026 — 25,250 members15 September 2026 — 25,224 members18 September 2026 — 25,195 members7 August 202618 September 2026
34 measurements spanning 42 days, net -386. 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 25,124–25,740 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 34
Measured (UTC)MembersChange
18 Sept 2026, 00:4125,195-29
15 Sept 2026, 21:1925,224-26
14 Sept 2026, 08:1825,250-15
12 Sept 2026, 16:0125,265-28
10 Sept 2026, 18:1925,293-39
7 Sept 2026, 14:1925,332-34
4 Sept 2026, 16:4225,366-26
3 Sept 2026, 01:1725,392-14
1 Sept 2026, 21:1825,406-11
1 Sept 2026, 00:4425,417-15
31 Aug 2026, 01:4925,432-9
29 Aug 2026, 22:1725,441-11
29 Aug 2026, 00:1325,452-18
27 Aug 2026, 23:1225,470-28
26 Aug 2026, 22:4925,498-9
25 Aug 2026, 21:4825,507-20
24 Aug 2026, 22:1425,527-23
23 Aug 2026, 09:4825,550-19
22 Aug 2026, 00:1425,569-17
20 Aug 2026, 15:3825,586first reading

Engagement

No public post preview. We read this entry on 15 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

Mentions

Named by 10 registered channels — 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.

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

“ОТЗОВИК WILDBERRIES | КАТАЛОГ | КУПЛЮ | БАРТЕР” (@OtzovikWildberries), 25,195 members as measured 18 September 2026. Telegram Register, tgregister.com/channel/OtzovikWildberries.

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.