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
Filings indexed 1,147 across all filing types
Latest filing 2024-04-29 Audit Report / Informat…
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 2023 - podpis MSz
Audit Report / Information Classification · 95% confidence The provided document text consists entirely of XML structures related to digital signatures, specifically containing elements like 'Signatures', 'SignedInfo', 'SignatureValue', 'KeyInfo', 'X509Certificate', and 'QualifyingProperties'. This structure is characteristic of an XML Digital Signature (XML-DSig) block, often used to secure official electronic documents in compliance with eIDAS or similar regulations. The presence of Polish organizational names (like 'Krajowa Izba Rozliczeniowa S.A.') and the reference URI containing Polish text ('o%C5%9Bwiadczenia%20do%20skonsolidowanego%20raportu%20rocznego%202023.xhtml') strongly suggests this is a security wrapper for a Polish corporate filing. The URI explicitly mentions 'skonsolidowanego raportu rocznego 2023', which translates to 'consolidated annual report 2023'. Since this is the signature block and not the report content itself, and it pertains to an annual report, the most appropriate classification is the general 'Regulatory Filings' (RNS) as a fallback for a signature block, or potentially related to the Annual Report (10-K) if the content was the report. However, given the structure is purely cryptographic metadata, RNS is the safest classification for a non-content filing component, or if we strictly interpret the URI reference, it points towards an Annual Report context. Since the document is not the report itself but the signature, and it doesn't fit the RPA definition (which usually announces a report), RNS is the best fit for this metadata artifact. FY 2023
2024-04-29 Polish
oświadczenia do raportu rocznego GK TD 2023 - podpis JŁ
Audit Report / Information Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, Object, QualifyingProperties). This structure is characteristic of a digitally signed document, often used to certify the authenticity and integrity of an underlying file. The reference URI within the signature block points to 'o%C5%9Bwiadczenia%20do%20skonsolidowanego%20raportu%20rocznego%202023.xhtml', which translates to 'statements for the consolidated annual report 2023'. Since the text provided is only the signature wrapper and not the content of the report itself, and it explicitly references an 'annual report' (raportu rocznego), this document is most likely an announcement or certification related to the filing of that report, rather than the report (10-K) or a general regulatory filing (RNS). Given the context of financial reporting, the most appropriate classification for a document that announces or certifies the publication of a major report, especially when the content is just metadata/signature, is Report Publication Announcement (RPA). However, since the content is purely technical signature data and not a narrative announcement, and it is clearly tied to a specific regulatory filing (Annual Report), the fallback category for miscellaneous regulatory filings (RNS) is also plausible if RPA is too specific for pure signature blocks. Given the strong link to the 'annual report' and the nature of the text being a certification/signature wrapper, it strongly suggests the *publication* of that report. I will lean towards RPA as it signifies the act of making the certified document available, which is what a signature block often accompanies or represents in a filing system. FY 2023
2024-04-29 Polish
oświadczenia do raportu rocznego GK TD 2023
Audit Report / Information Classification · 95% confidence The document text contains HTML structure, CSS styling, and metadata (title: 259400EX361KZAXTL620) typical of a web-based regulatory filing or report publication. The content is a technical rendering of a document (likely a PDF converted to HTML) rather than a specific financial report like a 10-K or Earnings Release. Given the lack of specific financial data or narrative content and the presence of technical formatting, it is best classified as a general regulatory filing. Q2 2024
2024-04-29 Polish
Oświadczenie o stosowaniu ładu korporacyjnego GK TD 2023 - podpis MSz
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, X509Data, etc.). This structure is characteristic of a digitally signed document, often used to attest to the authenticity and integrity of an underlying file. The presence of Polish language elements (like 'Oświadczenie o stosowaniu ładu korporacyjnego TD SA 2023.xhtml' referenced in the URI) and the certificate details suggest a formal regulatory filing or official document from a Polish entity that has been electronically signed. Since the text provided is *only* the signature block and not the content of the actual report (which is referenced as an XHTML file), this document is best classified as a general Regulatory Filing (RNS) or potentially an attachment/metadata related to a filing. Given the highly specific nature of the other codes, and the fact that this is metadata/signature rather than the report content itself, RNS (Regulatory Filings - general/miscellaneous) is the most appropriate fallback, as it doesn't fit clearly into ER, 10-K, or IR. However, the referenced file name 'Oświadczenie o stosowaniu ładu korporacyjnego' translates to 'Statement on Corporate Governance'. A statement on corporate governance often relates to the Governance Information (CGR) category. But because we only have the signature block, and not the content, we must rely on the 'MENU VS MEAL' rule. This is metadata about a filing, not the filing itself. Therefore, RNS is the safest classification for the signature block itself.
2024-04-29 Polish
Oświadczenie o stosowaniu ładu korporacyjnego GK TD 2023 - podpis JŁ
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML Digital Signature elements, specifically related to signing a document identified by the URI 'Oświadczenie o stosowaniu ładu korporacyjnego TD SA 2023.xhtml'. This structure strongly suggests a digitally signed document, likely a regulatory filing or official statement, rather than the content of a standard financial report (like 10-K, IR, or ER). The presence of Polish characters and the issuer name ('Krajowa Izba Rozliczeniowa S.A.') indicates a Polish entity. Since the content is the signature block itself and not the report it authenticates, and given that it relates to corporate governance ('o stosowaniu ładu korporacyjnego' translates to 'on the application of corporate governance'), the most fitting category is Governance Information (CGR). However, because the document provided is *only* the signature block and not the actual governance report, and it is a specific regulatory artifact, it could also be classified as a general Regulatory Filing (RNS) if CGR is too specific for the signature artifact itself. Given the explicit reference to 'corporate governance' in the signed URI, CGR is the best fit for the *subject matter* being signed, but since the document is just the signature, RNS is a safer fallback for an artifact that isn't the primary report. I will lean towards RNS as the document provided is the signature artifact, not the governance report itself, and it is a regulatory action.
2024-04-29 Polish
Oświadczenie o stosowaniu ładu korporacyjnego GK TD 2023
Audit Report / Information Classification · 95% confidence The document text provided is heavily truncated and appears to be the raw HTML/XML structure of a rendered document, including CSS styles and font definitions, rather than the substantive content of a financial filing. There are no clear keywords, regulatory headers (like '10-K', 'Annual Report', 'Earnings Release'), or specific reporting periods mentioned in the visible text that would allow for definitive classification based on the provided definitions. Given the lack of content and the presence of only structural markup, this document cannot be classified into any of the specific financial filing types (AGM-R, 10-K, ER, IR, etc.). The most appropriate fallback category for a document that doesn't fit neatly into the specific categories, especially when the content is unreadable or structural, is 'Regulatory Filings' (RNS), as it serves as a general catch-all for miscellaneous or unclassifiable regulatory submissions. However, since the document length is very large (985,892 chars), it suggests a full report was intended, but the provided text is just the wrapper. If forced to choose based on the structure being present, RNS is the safest fallback. If the document were short and announced a report, RPA would be chosen. Since the length is large, I will default to RNS as the general regulatory catch-all for unclassifiable content. Q3 2024
2024-04-29 Polish

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.