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 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
Sprawozdanie audytora z badania sprawozdania finansowego TD SA 2023 - podpis MSz
Audit Report / Information Classification · 95% confidence The provided document text consists entirely of XML structures related to digital signatures, specifically referencing 'Signatures', 'SignedInfo', 'SignatureValue', 'KeyInfo', and 'X509Certificate'. It also references a file named 'Sprawozdanie z badania TD SA_2023.xhtml' (which translates to 'Audit Report TD SA_2023.xhtml'). The presence of 'Sprawozdanie z badania' (Audit Report) strongly suggests this is related to an audit or examination report. Since the text itself is the signature block and not the full report content, and given the specific mention of an 'Audit Report' file, the most appropriate classification is Audit Report / Information (AR). The document length (5297 chars) is substantial enough to be a standalone report or a significant part of one, but the content is purely metadata/security, which often accompanies formal reports. FY 2023
2024-04-29 Polish
Sprawozdanie audytora z badania sprawozdania finansowego TD SA 2023 - podpis JŁ
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, etc.). This structure is typical for verifying the authenticity and integrity of an attached or referenced document, often seen in regulatory filings submitted electronically. The presence of Polish language elements (e.g., 'Sprawozdanie z badania TD SA 2023.xhtml', 'Krajowa Izba Rozliczeniowa S.A.') suggests a filing from a Polish entity. Since the content is purely the signature metadata and not the substantive report itself (which is referenced as 'Sprawozdanie z badania TD SA_2023.xhtml' - 'Audit Report'), and given the lack of specific financial reporting headers (like 10-K, ER, IR), this document is best classified as a general Regulatory Filing (RNS) or potentially an Audit Report (AR) if the referenced file was the primary content. However, based strictly on the provided text, which is the signature block, it functions as a regulatory attachment/proof of submission. Given the reference to 'Sprawozdanie z badania' (Audit Report), and the document being too short and structural to be the full report, it is most likely an accompanying document or the filing wrapper. Since 'AR' is for the standalone audit report, and this is just the signature, 'RNS' (Regulatory Filings - fallback) is appropriate, although if the referenced file is the core, 'AR' might be intended. Given the context of financial documents, an audit report signature block strongly implies an Audit Report (AR) is the subject matter, even if the text itself is just the signature. I will lean towards AR as the implied document type being signed, but RNS is a strong secondary candidate if the text must strictly define the content. Given the explicit reference to an 'Audit Report' ('Sprawozdanie z badania'), I classify it as AR, assuming this signature block accompanies that report.
2024-04-29 Polish
Sprawozdanie audytora z badania sprawozdania finansowego TD SA 2023
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, including CSS styling and font definitions, rather than a concise announcement or a standard regulatory filing body. The presence of extensive HTML structure, CSS, and font embedding data strongly suggests this is the underlying source code of a rendered document, likely a comprehensive report or filing that has been converted to HTML for viewing. Given the massive size (1,024,999 chars) and the fact that it is not a short announcement (ruling out RPA/RNS based on length alone), it is most likely a full, comprehensive report. However, without any specific keywords like '10-K', 'Annual Report', 'Interim Report', or 'Financial Statements' visible in the truncated text (which only shows HTML boilerplate), classifying the exact *type* of comprehensive report is impossible. In such cases where the content is obscured by formatting code but the size indicates a full report, and no specific type is identifiable, the most appropriate classification is the general fallback for regulatory filings that don't fit specific categories, which is RNS, or if we must assume it is a comprehensive report based on size, we look for the most general report type. Since the text is dominated by HTML structure and not content, and we cannot confirm 10-K or IR, RNS (Regulatory Filings - general/fallback) is the safest classification for an unreadable, large, structured document. Revisiting the rules: Rule 2 (Menu vs Meal) applies to short documents announcing a report. This document is very long, suggesting it *is* the report content, even if it's poorly formatted source code. Since the document is massive and contains no discernible content keywords to distinguish between 10-K, IR, or AR, I will default to the most general comprehensive report category available, which is 'IR' (Interim/Quarterly Report) if it's not annual, or use the general fallback 'RNS' if it's truly unclassifiable. Given the context of financial databases, a large, unclassified document is often treated as a general regulatory filing. Let's check the definitions again. If it were a 10-K or IR, we would expect to see section headers or financial tables. Since we only see HTML/CSS, it's impossible to confirm the period. I will use RNS as the fallback for an unclassifiable, large document structure. FY 2023
2024-04-29 Polish
oświadczenia do raportu TD SA 2023 - podpis MSz
Regulatory Filings 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 report or filing. The presence of Polish characters and references to 'sprawozdania rocznego' (annual report) within the URI ('o%C5%9Bwiadczenia%20do%20jednostkowego%20sprawozodania%20rocznego%20TD%20SA%202023.xhtml') strongly suggests this is the signature block for a formal annual financial report from a Polish entity. Since the text provided is *only* the signature block and not the content of the annual report itself, and given the context of financial filings, this document is most likely the certification/signature component of a larger filing. However, based strictly on the provided definitions, a standalone signature block does not fit perfectly into 10-K (the report itself) or ER (Earnings Release). It is a component of a regulatory filing. Given the strong indication of an 'annual report' (sprawozdania rocznego), the underlying document is likely a 10-K equivalent. Since we only have the signature, and it's not an announcement of a report (RPA), the most appropriate classification for a document that is fundamentally a certified component of a major filing, especially when the underlying content points to an annual report, is often categorized under the main report type or as a general Regulatory Filing (RNS) if the structure is highly unusual. However, the presence of 'sprawozdania rocznego' (annual report) makes 10-K the most relevant context. Since this is just the signature, and it's not a standard SEC form, classifying it as a general Regulatory Filing (RNS) is the safest fallback for an unclassifiable, certified component, although it is highly related to the 10-K structure. Revisiting the definitions: None explicitly cover a 'Digital Signature Block'. The content points to an Annual Report (10-K). If this were the full 10-K, it would be 10-K. If it were an announcement of the 10-K, it would be RPA. Since it is the *signature* of a document referencing an annual report, and it's not a standard SEC form, RNS (Regulatory Filings - general fallback) is the best fit for this specific artifact, as it is a regulatory certification artifact rather than the report content or an announcement. However, if we assume the system expects the classification of the *document being signed*, and the URI clearly states 'sprawozdania rocznego' (annual report), 10-K is the intended category for the underlying document. Given the ambiguity, I will lean towards the most specific document type referenced in the metadata (Annual Report) while acknowledging the artifact is just the signature, classifying it as RNS as the artifact itself is a regulatory certification component.
2024-04-29 Polish
oświadczenia do raportu TD SA 2023 - podpis JŁ
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, Reference, DigestValue, KeyInfo, X509Certificate, etc.). This structure is characteristic of a digitally signed electronic document, often used for regulatory filings in Europe (indicated by Polish characters and references to 'Krajowa Izba Rozliczeniowa S.A.'). The presence of a reference URI containing 'sprawozdania rocznego TD SA 2023.xhtml' strongly suggests this is related to an annual report or financial statement for the year 2023. Since the content is the signature block itself and not the narrative report, and given the context of annual financial reporting, the most appropriate classification is the Annual Report (10-K), assuming this signature block authenticates the primary annual filing, even though the text is only the signature metadata. If the document were the actual report, it would be 10-K. However, since the text is purely the signature structure, it could also be interpreted as a generic regulatory filing (RNS) or an Audit Report (AR) if the underlying document is the audited statements. Given the explicit mention of 'sprawozdania rocznego' (annual report), 10-K is the best fit for the *underlying* document type being certified, but since this is just the signature wrapper, RPA or RNS might apply if it were a short announcement. Given the length (5322 chars) and the specific reference to an annual report, I will classify it as the Annual Report (10-K) as the signature is validating that specific document type, overriding the 'announcement' rule slightly because the content is the validation structure for a major report, not a simple announcement text.
2024-04-29 Polish
oświadczenia do raportu TD SA 2023
Audit Report / Information Classification · 95% confidence The document text contains HTML/CSS styling and metadata typical of a web-based document viewer or a PDF-to-HTML conversion. The content is highly technical and lacks the narrative structure of an annual report, earnings release, or presentation. It appears to be a technical file or a system-generated document related to a regulatory filing (indicated by the '259400EX361KZAXTL620' title). Given the lack of specific financial or corporate narrative content and the nature of the file structure, it is best classified as a general regulatory filing. Q2 2024
2024-04-29 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.