Skip to main content
Triton Development S.A. logo

Triton Development S.A. — Investor Relations & Filings

Ticker · TRI ISIN · PLASMOT00030 LEI · 259400EX361KZAXTL620 WAR Real estate activities
Open in API
Filings indexed 1,147 across all filing types
Latest filing 2025-04-30 Regulatory Filings
Country PL Poland
Listing WAR TRI

About Triton Development S.A.

https://www.tritondevelopment.pl/

Triton Development S.A. is a real estate development company specializing in residential construction. The company's portfolio includes a range of housing options such as apartments in multi-family buildings, single-family houses, and semi-detached homes. It focuses on creating modern, high-quality living spaces with functional architecture in convenient locations, often catering to the luxury and higher-standard market segments. The company collaborates with leading architectural and construction firms to deliver its projects.

Recent filings

Filing Released Lang Actions
oświadczenia do raportu rocznego GK TD 2024 - podpis MSz
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML structures related to digital signatures ('Signatures', 'SignedInfo', 'SignatureValue', 'X509Data', 'QualifyingProperties'). This structure is characteristic of a digitally signed document, often used to certify the authenticity and integrity of a primary filing. The reference URI within the signature block, 'o%C5%9Bwiadczenia%20do%20skonsolidowanego%20sprawozdania%20rocznego%20TD%20SA%202024.xhtml', translates to something related to 'consolidated annual report' in Polish. Since the text itself is only the signature block and not the content of the report, and it is a formal regulatory artifact, it is best classified as a general Regulatory Filing (RNS) or potentially an Audit Report (AR) if the underlying document is confirmed to be an audit report. Given the explicit mention of 'skonsolidowanego sprawozdania rocznego' (consolidated annual report) in the reference, the underlying document is likely a 10-K or AR. However, the document provided *is* the signature block, which often accompanies filings like AR or 10-K. Since the content is purely metadata/signature and not the report itself, and it's a formal certification, RNS is a safe fallback, but AR is more specific if we assume the signature certifies the audit report mentioned in the URI. Given the context of financial reporting, a signature block accompanying an annual or audit report is common. I will lean towards AR (Audit Report / Information) as the URI strongly suggests an annual financial statement context, even though the text is just the signature.
2025-04-30 Polish
oświadczenia do raportu rocznego GK TD 2024 - podpis JŁ
Audit Report / Information Classification · 95% confidence The provided document text consists almost entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, X509Data, Object, QualifyingProperties). This structure is typical for digitally signed regulatory filings or official documents in the Polish electronic filing system (indicated by Polish characters and issuer names like 'Krajowa Izba Rozliczeniowa S.A.'). The reference URI contains the text 'o%C5%9Bwiadczenia%20do%20skonsolidowanego%20sprawozdania%20rocznego%20TD%20SA%202024.xhtml', which translates to 'statements to the consolidated annual report TD SA 2024'. While the content points towards an Annual Report (10-K), the document itself is just the signature block, not the report content. Since this is a signature block for a consolidated annual report, and we must choose from the provided list, the closest match for a comprehensive yearly report is '10-K'. However, given the structure is purely metadata/signature and not the report content, and the document length is relatively short (5323 chars), it could potentially be an announcement of the report. But the presence of 'skonsolidowanego sprawozdania rocznego' (consolidated annual report) strongly suggests the underlying document is the Annual Report. In the absence of the actual report content, and given the explicit mention of the 'annual report' within the signature reference, classifying it as the Annual Report (10-K) is the most appropriate choice, assuming this signature block authenticates that specific filing type. FY 2024
2025-04-30 Polish
oświadczenia do raportu rocznego GK TD 2024
Regulatory Filings Classification · 95% confidence The document text provided is extremely short, consisting primarily of HTML structure, CSS styles, and a base64 encoded image data within an img tag. The visible text content is minimal and appears to be boilerplate or metadata related to rendering a document viewer (e.g., sidebar, page container, loading indicators, CSS styles). Crucially, there is no substantive financial data, regulatory language (like '10-K', '10-Q', 'Proxy Statement'), or specific report content (like 'Management Discussion and Analysis' or 'Audit Opinion'). The document length is large (696,959 chars), but the visible text is just the wrapper/viewer code. Given the lack of content and the structure suggesting a container for a document, this is most likely a placeholder or a wrapper file. Since it doesn't contain the actual report content but is a file associated with a filing, and it doesn't fit any specific content-based category (like ER, IR, 10-K), the most appropriate classification based on the provided definitions and the 'MENU VS MEAL' rule (which suggests short announcements are RPA/RNS) is the general fallback category for miscellaneous filings that don't fit elsewhere, which is Regulatory Filings (RNS). However, given the structure is clearly a viewer/container, it might also be an attachment that isn't the primary report. Since it's not an announcement *about* a report (RPA), RNS is the best fit for an unclassifiable structural file.
2025-04-30 Polish
Oświadczenie o stosowaniu ładu korporacyjnego GK TD 2024 - podpis MSz
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML signature blocks, specifically containing elements like 'Signatures', 'SignedInfo', 'SignatureValue', 'KeyInfo', and 'QualifyingProperties'. This structure is characteristic of a digitally signed document, often used to certify the authenticity and integrity of an official filing or document. The content itself does not describe financial results, management changes, or meeting details, but rather the cryptographic proof of signing. The reference URI within the signature block, 'Oświadczenie o stosowaniu ładu korporacyjnego TD SA 2024.xhtml', suggests the underlying document is a Corporate Governance Statement (or similar compliance document) for the year 2024. Since the text provided is only the signature block and not the content of the governance statement itself, and given the highly technical, non-narrative nature of the input, it is most appropriately classified as a general Regulatory Filing (RNS) or potentially a specific Governance Information document (CGR) if we assume the signature is attached to that type of report. However, because the input is purely the signature metadata and lacks the actual content of any defined report type (10-K, ER, IR, etc.), the safest and most general classification for an unidentifiable, signed technical attachment is RNS, as it represents a regulatory artifact that doesn't fit the content-based categories. Given the context of corporate filings, a signed governance statement would fall under CGR, but the text provided is the signature wrapper, making RNS the best fit for the wrapper itself, or we can infer the underlying document type. Given the URI mentions 'ładu korporacyjnego' (corporate governance), CGR is a strong candidate for the *intended* document, but RNS is better for the *provided text* which is just the signature. I will lean towards RNS as the fallback for technical/metadata filings that aren't the primary report content.
2025-04-30 Polish
Oświadczenie o stosowaniu ładu korporacyjnego GK TD 2024 - podpis JŁ
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML structures related to digital signatures, specifically using XML Digital Signature (ds:) and XAdES (xades:) namespaces. It contains elements like 'Signature', 'SignedInfo', 'SignatureValue', 'KeyInfo', and 'QualifyingProperties' with certificate details, signing time ('2025-04-28T11:52:35Z'), and digest values. This structure is characteristic of a digitally signed document, often used to certify the authenticity and integrity of another file (referenced in the 'Reference' URI: 'Oświadczenie o stosowaniu ładu korporacyjnego TD SA 2024 (1).xhtml'). Since the content is the signature block itself and not the underlying report, and given the context of corporate filings, this is most likely an attachment or metadata related to a formal filing. However, none of the specific filing types (10-K, ER, IR, etc.) are explicitly mentioned in the content. The presence of a signed statement ('Oświadczenie o stosowaniu ładu korporacyjnego' translates to 'Statement on Corporate Governance') suggests a governance or compliance document. Since the text is purely the signature block and not the report content, and it doesn't announce a report release (RPA), the most appropriate general category for an unclassified, formal, signed regulatory document is 'Regulatory Filings' (RNS), as it serves as a fallback for formal, non-standard content.
2025-04-30 Polish
Oświadczenie o stosowaniu ładu korporacyjnego GK TD 2024
Audit Report / Information Classification · 95% confidence The provided document text is extremely long (over 1 million characters) and appears to be the raw HTML/XML structure of a document, likely a PDF rendered as HTML, given the extensive use of CSS styling for layout (`<style>` tags, positioning classes like `.pf`, `.pc`, etc.). The length strongly suggests it is a comprehensive report rather than a short announcement. Since the text itself does not contain explicit headers like '10-K', 'Annual Report', or specific quarterly markers, but it is a very large, structured document, it is most likely a full regulatory filing or a comprehensive report. Given the context of financial documents, the most comprehensive annual report is the 10-K. However, without explicit textual confirmation of the filing type (like 'Form 10-K' or 'Annual Report'), and considering the document is a massive data dump, it could also be an Interim Report (IR) or a Financial Supplement (XLSX) if the content were tabular, but the structure suggests a narrative report. Since the length is substantial and it's not a short announcement, I will lean towards the most comprehensive report type available, the 10-K, or the comprehensive interim report (IR), as the content is too large to be an ER or RPA. Given the lack of specific period information, and the sheer size, I will classify it as a comprehensive report. If it were a quarterly report, it would be an IR. If it were the annual report, it would be a 10-K. Without explicit text, I must rely on the size. A document this large is almost certainly a full report. I will tentatively select 10-K as the default for a large, comprehensive, unclassified report, but acknowledge the ambiguity. Re-evaluating: The document structure is highly indicative of a rendered PDF viewer output, which often contains the full content of a filing. Given the options, and the massive size, it is a full report. I will select 10-K as the primary annual comprehensive report. Q3 2024
2025-04-30 Polish

Browse filings by year

11 years

Report missing filing

Can't find a specific document? Let us know and we'll add it within 24 hours.

We will notify you once the filing is added.
Report sent
Thank you. We will check the data and update it shortly.