Telegram RegisterThe public register of Telegram
Telegram profile photo for Фетхие Олюдениз🇹🇷Чат

Supergroup

Фетхие Олюдениз🇹🇷Чат

@fethiye_oludeniz

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

1,621members

+329 since we began measuring on 7 August 2026

41 online right now

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

Register entry

Telegram ID-1002474754166
TypeSupergroup
Username@fethiye_oludeniz
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live2 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/fethiye_oludeniz

Topic

Travel — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

1,2921,6291,460.57 August 2026 — 1,292 members7 August 2026 — 1,294 members10 August 2026 — 1,307 members14 August 2026 — 1,342 members17 August 2026 — 1,356 members20 August 2026 — 1,355 members23 August 2026 — 1,379 members26 August 2026 — 1,397 members29 August 2026 — 1,437 members1 September 2026 — 1,467 members4 September 2026 — 1,482 members9 September 2026 — 1,516 members13 September 2026 — 1,530 members17 September 2026 — 1,528 members27 September 2026 — 1,540 members27 September 2026 — 1,540 members5 October 2026 — 1,600 members11 October 2026 — 1,608 members14 October 2026 — 1,624 members18 October 2026 — 1,627 members20 October 2026 — 1,629 members23 October 2026 — 1,628 members27 October 2026 — 1,619 members2 November 2026 — 1,621 members1,6217 August 20262 November 2026
24 measurements spanning 86 days, net +329. 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 1,241–1,680 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
2 Nov 2026, 02:211,621+2
27 Oct 2026, 05:091,619-9
23 Oct 2026, 19:281,628-1
20 Oct 2026, 18:111,629+2
18 Oct 2026, 04:061,627+3
14 Oct 2026, 17:261,624+16
11 Oct 2026, 11:581,608+8
5 Oct 2026, 06:171,600+60
27 Sept 2026, 03:301,540no change
27 Sept 2026, 01:361,540+12
17 Sept 2026, 19:381,528-2
13 Sept 2026, 09:221,530+14
9 Sept 2026, 19:191,516+34
4 Sept 2026, 18:421,482+15
1 Sept 2026, 08:161,467+30
29 Aug 2026, 03:541,437+40
26 Aug 2026, 04:121,397+18
23 Aug 2026, 09:451,379+24
20 Aug 2026, 04:231,355-1
17 Aug 2026, 12:151,356first 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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“Фетхие Олюдениз🇹🇷Чат” (@fethiye_oludeniz), 1,621 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/fethiye_oludeniz.

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.