Telegram RegisterThe public register of Telegram
Telegram profile photo for Lotus Private Date

Channel

Lotus Private Date

@lotusprivate

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

101,514subscribers

-13,376 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002399536205
TypeChannel
Username@lotusprivate
DescriptionWebsite Güncel Giriş: https://lotusprivate.live/giris Hızlı Rezervasyon: @LPDateBot Sponsor Duyuru: @lotusprivatelive Sponsor Kod Duyuru: @lotusprivatekod Reklam ve işbirliği: @lotusprivatepr
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/lotusprivate

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 28% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@lotusprivatelive/9465 Aug 2026, 21:56 UTC@lotusprivate/2897 · this entry5 Aug 2026, 21:56 UTC1.00under a minute
@lotusprivate/2890 · this entry4 Aug 2026, 22:19 UTC@lotusprivatelive/9496 Aug 2026, 09:14 UTC1.0035 hours
@lotusprivate/2891 · this entry5 Aug 2026, 12:38 UTC@lotusprivatelive/9516 Aug 2026, 12:09 UTC1.0024 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@lotusprivatelive5 (5/5 hand-verifiable sample passed)1.0028 minutesthis entry (3–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 21 comparable posts for this entry, running 3 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @lotusprivate — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

101,514156,511129,012.57 August 2026 — 114,890 subscribers7 August 2026 — 114,890 subscribers8 August 2026 — 156,511 subscribers9 August 2026 — 136,671 subscribers10 August 2026 — 135,123 subscribers11 August 2026 — 134,272 subscribers12 August 2026 — 128,218 subscribers13 August 2026 — 124,745 subscribers14 August 2026 — 121,937 subscribers15 August 2026 — 121,303 subscribers16 August 2026 — 139,889 subscribers18 August 2026 — 138,331 subscribers18 August 2026 — 137,434 subscribers19 August 2026 — 133,913 subscribers20 August 2026 — 133,120 subscribers22 August 2026 — 130,020 subscribers23 August 2026 — 125,512 subscribers25 August 2026 — 123,684 subscribers26 August 2026 — 140,198 subscribers27 August 2026 — 139,863 subscribers28 August 2026 — 139,570 subscribers29 August 2026 — 139,037 subscribers30 August 2026 — 138,350 subscribers30 August 2026 — 137,806 subscribers1 September 2026 — 137,213 subscribers2 September 2026 — 136,647 subscribers3 September 2026 — 136,083 subscribers5 September 2026 — 134,645 subscribers8 September 2026 — 135,388 subscribers11 September 2026 — 131,697 subscribers13 September 2026 — 126,460 subscribers14 September 2026 — 122,501 subscribers16 September 2026 — 120,847 subscribers19 September 2026 — 118,753 subscribers25 September 2026 — 101,514 subscribers7 August 202625 September 2026
35 measurements spanning 49 days, net -13,376. 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 93,264–164,761 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
25 Sept 2026, 21:19101,514-17,239
19 Sept 2026, 02:41118,753-2,094
16 Sept 2026, 15:00120,847-1,654
14 Sept 2026, 19:19122,501-3,959
13 Sept 2026, 06:17126,460-5,237
11 Sept 2026, 06:36131,697-3,691
8 Sept 2026, 13:17135,388+743
5 Sept 2026, 06:01134,645-1,438
3 Sept 2026, 08:15136,083-564
2 Sept 2026, 05:23136,647-566
1 Sept 2026, 02:59137,213-593
30 Aug 2026, 22:58137,806-544
30 Aug 2026, 02:04138,350-687
29 Aug 2026, 01:37139,037-533
28 Aug 2026, 02:23139,570-293
27 Aug 2026, 03:08139,863-335
26 Aug 2026, 00:43140,198+16,514
25 Aug 2026, 03:43123,684-1,828
23 Aug 2026, 19:27125,512-4,508
22 Aug 2026, 03:34130,020first reading

Engagement

490 posts held, back to 3 August 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 116 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.04%
avg views ÷ 101,514 subscribers
Avg views / post
9,180
271 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
278
of 490 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 September 2026
Posts held490 (3 August 2026 – 30 September 2026)
Views total2,486,862
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 11:35 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,650
Videos
≈59
Links
≈793

Lifetime counters from Telegram’s own channel header, read 30 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
4m 27s
Average length
38s

Measured directly from 7 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

30 Sept 2026, 10:00 UTC205 viewsread 30 September 2026
Photo

Lotus Private'ın PREMIUM Modeli Svetlena ile tanışın! Svetlena'nın detaylı görsellerine, konum ve servis bilgilerine Lotus Private VIP Telegram kanalımızdan inceleyebilirsiniz!

30 Sept 2026, 09:00 UTC547 viewsread 30 September 2026
Photo

Bazı duruşlar, kelimelerden daha fazlasını anlatır. 🖤 Siyahın asaleti, sade çizgiler ve kendinden emin bir bakış… Lotus Private’ın estetik anlayışı, her detayda kendini hissettirir. Gösterişe ihtiyaç duymayan, kendi tarzıyla iz bırakan bir zarafet. Lotus Private — İmzamız detaylarda. 1️⃣Aramıza Katıl | lotusprivate.live

29 Sept 2026, 20:00 UTC≈3,970 viewsread 30 September 2026
Photo

💲KAYIT OL, 500 TL NAKİT KAZAN! 🚫SİTE BAKİYESİ DEĞİL! 🚫PUAN DEĞİL! 🚫ÇEVRİM ŞARTI YOK! ➡️DİREKT CÜZDANINIZA, 💰NAKİT 500 TL!💰 🎉 Lotus Private'tan size 500 TL kayıt ödülü! 1️⃣500 TL Nakit Kazan | lotusprivate.live

29 Sept 2026, 19:00 UTC≈5,140 viewsread 30 September 2026
Photo

Lotus Private'ın VIP Modeli Vlada ile tanışın! Vlada'nın detaylı görsellerine, konum ve servis bilgilerine Lotus Private VIP Telegram kanalımızdan inceleyebilirsiniz!

29 Sept 2026, 18:01 UTC≈5,200 viewsread 30 September 2026
Photo

Lotus Private'ın PREMIUM Modeli Rana ile tanışın! Rana'nın detaylı görsellerine, konum ve servis bilgilerine Lotus Private VIP Telegram kanalımızdan inceleyebilirsiniz!

29 Sept 2026, 17:00 UTC≈5,240 viewsread 30 September 2026
Photo

Lotus Private'ın PREMIUM Modeli Elisa ile tanışın! Elisa'nın detaylı görsellerine, konum ve servis bilgilerine Lotus Private VIP Telegram kanalımızdan inceleyebilirsiniz!

29 Sept 2026, 16:00 UTC≈5,280 viewsread 30 September 2026
Photo

Lotus Private'ın PREMIUM Modeli Bahar ile tanışın! Bahar'ın detaylı görsellerine, konum ve servis bilgilerine Lotus Private VIP Telegram kanalımızdan inceleyebilirsiniz!

29 Sept 2026, 13:00 UTC≈5,290 viewsread 30 September 2026
Photo

Lotus Private'ın PREMIUM Modeli Olga ile tanışın! Olga'nın detaylı görsellerine, konum ve servis bilgilerine Lotus Private VIP Telegram kanalımızdan inceleyebilirsiniz!

29 Sept 2026, 11:00 UTC≈5,630 viewsread 30 September 2026
Photo

Lotus Private'ın PREMIUM Modeli Angelina ile tanışın! Angelina'nın detaylı görsellerine, konum ve servis bilgilerine Lotus Private VIP Telegram kanalımızdan inceleyebilirsiniz!

29 Sept 2026, 09:31 UTC≈5,680 viewsread 30 September 2026
Photo

LOTUS PRIVATE YENİ SPONSORU HİTBET! Bağlantımızdan kayıt olarak 65,000 TL'ye kadar hoşgeldin bonusundan faydalanabilirsiniz!

29 Sept 2026, 09:01 UTC≈5,560 viewsread 30 September 2026
Photo

1️⃣ | LotusHUB ⭐️ İhtiyacınız olan her şey Lotus Private'ta. • 500'den fazla onaylı model ile Türkiye'nin en büyük escort ajansı olarak yerini korumaya devam ediyor! • Private partileriyle Türkiye'nin, hatta dünyanın en önemli kişilerini bir araya toplayan Lotus Private; güçlü misafir kitlesine onlara yaraşır bir eğlence sunuyor. • Özel rezervasyon etkinlikleri ve lüks ödüllere sahip çekilişleriyle her kesimden g…

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

Posts edited after publishing

@lotusprivate edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
13 September 2026

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

“Lotus Private Date” (@lotusprivate), 101,514 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/lotusprivate.

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.