Telegram RegisterThe public register of Telegram
Telegram profile photo for Titanic⛵️🛳3.net

Channel

Titanic⛵️🛳3.net

@titanic33

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

11,826subscribers

-774 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001471072796
TypeChannel
Username@titanic33
Description❤️‍🔥TITANIC FOR FREE INTERNET❤️‍🔥 ✅انترنت مجاني خاص بجميع الشبكات ❤️‍🔥 ✅فودافون-اورانج-وي-اتصالات❤️‍🔥 ✅بوتات انترنت مجاني ❤️‍🔥 ✅كونفجات انترنت ❤️‍🔥
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/titanic33

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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.

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
@titanic_3345/407725 Jul 2026, 15:07 UTC@titanic33/6575 · this entry7 Aug 2026, 17:19 UTC1.0013 days
@titanic33/6568 · this entry28 Jul 2026, 23:44 UTC@titanic_3345/408528 Jul 2026, 23:44 UTC1.00under a minute
@titanic_3345/413624 Oct 2026, 15:18 UTC@titanic33/6633 · this entry24 Oct 2026, 15:19 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@titanic_334510 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–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. 2 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 26 comparable posts for this entry, running 28 July 2026 to 18 November 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @titanic_3345. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 19 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

11,82612,60012,2137 August 202617 November 2026
65 measurements spanning 102 days, net -774. 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 11,710–12,716 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
17 Nov 2026, 12:3711,826-26
14 Nov 2026, 04:1811,852-29
11 Nov 2026, 06:5811,881-9
9 Nov 2026, 10:4811,890-19
8 Nov 2026, 04:0111,909-9
7 Nov 2026, 03:5911,918-9
6 Nov 2026, 06:4011,927-15
5 Nov 2026, 04:1911,942-6
4 Nov 2026, 07:1711,948-8
3 Nov 2026, 09:5611,956-11
2 Nov 2026, 06:4611,967-5
1 Nov 2026, 04:4811,972-4
31 Oct 2026, 07:1511,976-2
30 Oct 2026, 04:4011,978-7
29 Oct 2026, 05:4111,985-8
28 Oct 2026, 00:1011,993-4
26 Oct 2026, 22:0611,997-4
25 Oct 2026, 00:2012,001-6
24 Oct 2026, 01:4712,007-4
22 Oct 2026, 23:4012,011first reading

Engagement

66 posts held, back to 25 July 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 85 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.6%
avg views ÷ 11,826 subscribers
Avg views / post
2,670
32 posts measured
Reaction rate
0.659%
reactions ÷ views · ER floor
Posts in window
32
of 66 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 18 November 2026
Posts held66 (25 July 2026 – 18 November 2026)
Views total85,391
Reactions total563
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Nov 2026, 12:37 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
≈769
Videos
≈146
Links
≈514

Lifetime counters from Telegram’s own channel header, read 19 November 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
1m 42s
Average length
51s

Measured directly from 2 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.

Reaction mix

973 reactions across 65 posts, in 26 distinct kinds. The most used accounts for 77.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤75277.3%
👍434.42%
🤔434.42%
😁212.16%
🥰131.34%
😢111.13%
🤩90.925%
👏80.822%
🤯80.822%
🌚70.719%
🔥70.719%
😎70.719%
💔60.617%
👌50.514%
🗿50.514%
😈50.514%
😡50.514%
🥴50.514%
👻30.308%
🤓30.308%
6 further kinds70.719%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 65 of the 66 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 973 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 66 most recent posts we hold, published 25 July 2026 to 18 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 7 of 32 posts held from the last 30 days (21.9%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

18 Nov 2026, 19:26 UTC577 views15 reactionsread 19 November 2026

https://t.me/Titanic_33/s/1 إلي أحدهم 👌❤️

❤11🔥4

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

18 Nov 2026, 16:42 UTC823 views31 reactionsread 19 November 2026

بصوا ي شباب بما أن انا كنت قايل أن مفيش ضمان علي الباقه بعد ما انا افعلها 👌 ف دي حاجه مني ليكم اي حد انا فعلت ليه ال 45 جيجا والباقه اتسحبت منه انا هرجع له فلوسه واحاسبه فقط علي التفعيل 👌 @Titanic_33 وهرد علي الكل بس اخلص ال ورايا الاول 👌❤️

❤31

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

18 Nov 2026, 14:50 UTC991 views32 reactionsread 19 November 2026

والله العظيم مبسوط لأن في شوية بهايم مفكرين لما الثغره تنزل وبشكل مجاني انت كده الواد الروش ال مفيش من امك اتنين ال عاملي بوت ول عملي فيديو نشرها علي الفيس واليوتيوب والتيك توك اه مستنين اي تاني تعملوه وعاوزينها تكمل يومين مجال بقي وسخ وبقي فيه شوية اطفال حرفيا عاملين شوية قنوات غرضهم قفل الثغرات مش اكتر مش إفادة الناس 👌

❤24👻3👏2😢2🥴1

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

17 Nov 2026, 21:29 UTC≈1,250 views16 reactionsread 19 November 2026

بعشقكم وانا حاطط عليكم واحد واحد 😂✅❤️ هقول هالك انت وهو 😂 ربنا يهديكم واعيش دايما واديكم 😎♥️

❤12🤔3👏1

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

17 Nov 2026, 21:00 UTC≈1,270 views12 reactionsread 19 November 2026

ي شباب ال كان باعت يبعت ✅❤️ والعرض مازال ساري ✅❤️ ب 150 كاش بدلا من 250 كاش ✅ @Titanic_33

❤8💔2🔥1😭1

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

17 Nov 2026, 18:34 UTC≈1,370 views7 reactionsread 19 November 2026

روقوا عليه 01019920636 01108791067 وحيات امك ل هعرفك ✅❤️ وهخليك تقول حقي براقبتي 👌 @zPqzhdk

👍4❤2💔1

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

17 Nov 2026, 14:13 UTC≈1,420 views15 reactionsread 19 November 2026

ال عاوز يفعل يبعت يلا ✅ عرض ولمدة ساعتين فقط السعر 150 كاش بدلا من 250 ✅❤️ @Titanic_33

🌚7❤5🤓2🐳1

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

17 Nov 2026, 14:09 UTC≈1,420 views4 reactionsread 19 November 2026

روقوا عليه 😴 01133083005 01028570582 01127948682

👍4

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

16 Nov 2026, 20:54 UTC≈1,490 views14 reactionsread 19 November 2026

🔥 متاح التفعيل لخطوط اتصالات 🔥 📦 45 جيجا إنترنت 💰 السعر: 250 جنيه كاش ⏳ المدة: 28 يوم ✅ عادي لو مستلف أو عليك مديونية 📩 ابعت الرقم فقط أو الإيميل والباسورد. 🚫 لا يوجد أي ضمان 📲 @Titanic_33

❤13🤔1

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

12 Nov 2026, 14:40 UTC≈2,400 views13 reactionsread 19 November 2026
Sticker

Sticker, posted without a caption

😎7❤4💯1🤯1

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

10 Nov 2026, 22:11 UTC≈2,780 views30 reactionsread 19 November 2026

مع العلم يعتبر كل الناس ال كانت مفعله معايا تم استرجاع الباقه ليهم جميعا 👌❤️ الا بعض الناس بسبب اسلوبهم وعدم تقديرهم 👌

❤27👍3

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

10 Nov 2026, 22:08 UTC≈2,700 views29 reactionsread 19 November 2026

قسما بالله الواحد غلطان بجد أن بحاول اقدر ناس واتعامل معاكم بحترام بس هتضطروني اعاملكم ميري لان لو اخدت بالكم أن انا كنت بنزل بوست تفعيل باقات اتصالات وكاتب فيه مفيش ضمان علي الباقه يعني لو حصل اي حاجه بعد التفعيل انا غير مسؤول ✅ وان انا ارجعلك الباقه دي حاجه زوقيا مني ليكم✅ لاكن انا مش مضطر ارجعلك الباقه علشان تكون عارف 👌 ف لو حسيت في أسلوبك قلة احترام ملكش حاجه عندي ✅

❤27👍2

Signed EL̑S̑ȂY̑ȆD̑ 𓅓 𓃠

Showing the 12 most recent of 66 posts we hold for @titanic33. 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 recorded as deleted after publishing

We recorded 7 posts on @titanic33 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
23 hours
Seen missing in the last 30 days
4

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

“Titanic⛵️🛳3.net” (@titanic33), 11,826 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/titanic33.

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.