Telegram RegisterThe public register of Telegram
Telegram profile photo for Marketologlar | O'zbekiston

Supergroup

Marketologlar | O'zbekiston

@marketologlar_guruhi

Has discussion group

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

2,981members

+95 since we began measuring on 7 August 2026

68 online right now

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001308284063
TypeSupergroup
Username@marketologlar_guruhi
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 September 2026
Last confirmed live29 October 2026
Measurements held22
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/marketologlar_guruhi

Topic

Marketing & affiliate — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 the other topics.

Growth

2,8772,9812,9297 August 2026 — 2,886 members7 August 2026 — 2,889 members10 August 2026 — 2,897 members13 August 2026 — 2,885 members16 August 2026 — 2,877 members19 August 2026 — 2,891 members22 August 2026 — 2,895 members25 August 2026 — 2,922 members27 August 2026 — 2,921 members31 August 2026 — 2,942 members2 September 2026 — 2,940 members8 September 2026 — 2,903 members12 September 2026 — 2,903 members12 September 2026 — 2,923 members16 September 2026 — 2,929 members29 September 2026 — 2,943 members6 October 2026 — 2,950 members13 October 2026 — 2,952 members16 October 2026 — 2,958 members22 October 2026 — 2,964 members25 October 2026 — 2,978 members29 October 2026 — 2,981 members7 August 202629 October 2026
22 measurements spanning 83 days, net +95. 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 2,861–2,997 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 22
Measured (UTC)MembersChange
29 Oct 2026, 00:372,981+3
25 Oct 2026, 13:592,978+14
22 Oct 2026, 10:292,964+6
16 Oct 2026, 04:362,958+6
13 Oct 2026, 00:462,952+2
6 Oct 2026, 05:572,950+7
29 Sept 2026, 08:212,943+14
16 Sept 2026, 04:582,929+6
12 Sept 2026, 21:402,923+20
12 Sept 2026, 01:182,903no change
8 Sept 2026, 14:562,903-37
2 Sept 2026, 22:292,940-2
31 Aug 2026, 00:262,942+21
27 Aug 2026, 18:472,921-1
25 Aug 2026, 05:232,922+27
22 Aug 2026, 13:282,895+4
19 Aug 2026, 13:142,891+14
16 Aug 2026, 07:052,877-8
13 Aug 2026, 02:542,885-12
10 Aug 2026, 02:022,897first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“Marketologlar | O'zbekiston” (@marketologlar_guruhi), 2,981 members as measured 29 October 2026. Telegram Register, tgregister.com/channel/marketologlar_guruhi.

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.