Skip to main content
Torpol S.A. logo

Torpol S.A. — Investor Relations & Filings

Ticker · TOR ISIN · PLTORPL00016 LEI · 259400HHPUDSWFR70D07 WAR Construction
Filings indexed 1,036 across all filing types
Latest filing 2023-03-11 Management Reports
Country PL Poland
Listing WAR TOR

Torpol S.A. is an engineering and construction company specializing in the comprehensive modernization and construction of railway infrastructure. The company's services encompass the design and implementation of complex projects, including the building and upgrading of railway tracks, lines, and stations to meet European and international standards. Torpol has experience in adapting railway lines for high-speed passenger traffic. The company also engages in the development of urban infrastructure.

Recent filings

Filing Released Lang Actions
Ocena RN dot. Sprawozdania Zarządu z działalności i JSF za 2022
Management Reports Classification · 99% confidence The document is titled "Ocena Rady Nadzorczej TORPOL S.A. dotycząca sprawozdania z działalności emitenta i sprawozdania finansowego..." (Assessment of the Supervisory Board of TORPOL S.A. regarding the management report and financial statement...). It explicitly references the audit report ('badania sprawozdania finansowego Emitenta za rok obrotowy 2022 i wydaniem opinii bez zastrzeżeń') and details the findings of the Supervisory Board concerning the financial statements and management report for the year 2022. This content strongly aligns with the scope of an Audit Report or Information document, which covers standalone audit reports, applied accounting principles, and results of internal/regulatory stress tests, as opposed to the full Annual Report (10-K) or just an Earnings Release (ER). The focus is on the review and validation of the financial reporting process and results by the supervisory body, supported by the external auditor's opinion. Therefore, 'AR' (Audit Report / Information) is the most appropriate classification.
2023-03-11 Polish
Sprawozdanie biegłego z badania_2022 - podpis
Audit Report / Information Classification · 95% confidence The provided document text consists almost entirely of XML structures related to digital signatures (Signature, SignedInfo, SignatureValue, KeyInfo, Object, QualifyingProperties, etc.). This structure is characteristic of digitally signed regulatory filings or documents where integrity and authenticity are paramount, often seen in XBRL or similar structured data submissions. Crucially, the content does not contain typical narrative elements of an Annual Report (10-K), Interim Report (IR), Earnings Release (ER), or Investor Presentation (IP). It lacks financial tables, management discussion, or forward-looking statements. However, the presence of extensive digital signature metadata, including references to certificates and timestamps, strongly suggests this is a wrapper or metadata file associated with a formal regulatory submission, rather than the primary content document itself. The reference URI within the signature block points to "22 Torpol audit report JSF.xhtml", which hints at an Audit Report (AR) being signed, but the document *itself* is the signature block. Given the options, this XML signature block is a component of a regulatory filing process. Since it is not the report content (like AR) but the mechanism verifying it, and it doesn't fit neatly into announcement categories (RPA/RNS) which usually contain brief text *about* the report, the most appropriate classification for a document that is purely technical metadata/signature data related to compliance is the general fallback category for regulatory filings that don't fit elsewhere, or potentially an Audit Report (AR) if we assume the signature is attached to that specific document type. Since the content is purely technical signature data and not the narrative report, and it's not an announcement *of* a report, it is best categorized as a general Regulatory Filing (RNS) or potentially an Audit Report (AR) if the underlying document is implied. Given the explicit reference to an 'audit report' in the digest URI, 'AR' is a strong candidate for the *underlying* document type, but the current document is the signature wrapper. In many databases, such signature wrappers are often grouped with the primary filing type or as a general regulatory filing. Considering the definitions, 'AR' (Audit Report / Information) is the closest thematic fit based on the URI reference, even though the text is the signature wrapper. If the system expects the classification of the *content being signed*, AR is plausible. If it expects the classification of the *file provided*, RNS (Regulatory Filings - fallback) is safer. Given the high specificity required, and the explicit mention of 'audit report' in the reference, I will lean towards AR, assuming the signature is inseparable from the audit document context, but acknowledge the ambiguity. Let's re-evaluate based on the 'Menu vs Meal' rule: This is not the meal (AR), but the packaging/verification (RNS/Wrapper). Therefore, RNS is the most accurate classification for the provided text structure itself. Final decision: The document is the digital signature wrapper for what appears to be an audit report. This wrapper structure itself is a technical regulatory artifact, best classified as RNS (Regulatory Filings - fallback for miscellaneous filings). FY 2022
2023-03-11 Polish
Sprawozdanie biegłego z badania_2022
Audit Report / Information Classification · 99% confidence The document text is extremely short ('22 Torpol audit report JSF') and explicitly contains the phrase 'audit report'. Based on the definitions, 'Audit Report / Information' (AR) is the most appropriate classification, as it covers standalone audit reports. The short length suggests it might be an announcement or a reference to the report, but the explicit mention of 'audit report' strongly points to AR over a general RPA or RNS. FY 2022
2023-03-11 English
List Prezesa TORPOL SA_2022 - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, X509Data, Object, QualifyingProperties). The reference URI within the signature block points to 'TOR_ListCEO_2022_2022-12-31_pl.xhtml'. This strongly suggests the document is a digitally signed file, likely related to a list of CEOs or management information, dated December 31, 2022. Since the content is purely the signature structure and not the actual report content, and it relates to management/director information (CEO list), the most fitting category is Board/Management Information (MANG). However, given the highly technical, non-narrative nature of the text (pure XML signature), it could also be interpreted as a general regulatory filing or an attachment. Given the explicit reference to 'ListCEO', MANG is the primary intent, but because the document *is* the signature block and not the actual filing, and it doesn't explicitly announce a report release (RPA), it falls into a specific regulatory context. Since MANG is about changes in management, and this is a signed document related to a list of CEOs, MANG is the best fit for the *subject matter* indicated by the URI. If the URI pointed to a general report, RNS would be used. Since the URI points to a specific management-related document, MANG is chosen.
2023-03-11 Polish
List Prezesa TORPOL SA_2022
Management Reports Classification · 95% confidence The document is a letter from the CEO of TORPOL S.A. summarizing the company's financial performance, operational highlights, and strategic outlook for the 2022 fiscal year. It provides specific financial figures (EBITDA, net profit, cash position) and discusses management's perspective on business trends, market challenges, and future outlook. This content aligns with the definition of a Management Discussion and Analysis (MDA) report, as it serves as the management's detailed explanation of financial results and business trends. FY 2022
2023-03-11 Polish
Raport Niefinansowy_2022 - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML digital signature blocks ('Signature', 'SignedInfo', 'SignatureValue', 'KeyInfo', 'X509Certificate', etc.). This structure is typical for documents that have been digitally signed for authenticity and integrity, often found within regulatory filings like XBRL or XML-based submissions. Crucially, the references within the signatures point to a URI: "GKTOR_RNF2022_2022-12-31_pl.xhtml". The presence of 'RNF' (likely standing for Raport Okresowy Finansowy - Periodic Financial Report in Polish context, given the Polish certificate issuers) and the date '2022-12-31' strongly suggests this is related to a periodic financial report. However, the document *itself* is not the financial report content (like a 10-K or IR); it is the metadata/signature wrapper for the report. Given the options: 1. It is not a full report (10-K, IR, ER) because we only see signatures. 2. It is not an AGM-R, MANG, CT, etc., as the content is purely technical signatures. 3. The presence of 'RNF' (Periodic Financial Report) points towards an Interim/Quarterly Report (IR) or Annual Report (10-K), but since this is just the signature block, it is most likely an attachment or a component of a larger filing. 4. Since the content is technical metadata (signatures) related to a financial report (implied by RNF and date), and it doesn't fit neatly into the content-based categories, the most appropriate fallback for technical/miscellaneous regulatory components that aren't the main report body is 'RNS' (Regulatory Filings) or potentially 'XLSX' if it were data, but 'RNS' is the best general regulatory fallback for non-standard content. Revisiting the definitions, if this were an announcement *about* the report, it would be RPA. Since this is the digital signature *of* the report file itself (indicated by the URI pointing to the XHTML file being signed), and it's not the content, it's a component of a regulatory submission. In many databases, the signature block itself, when extracted separately, falls under the general regulatory filing category if the primary content classification is ambiguous or missing. Considering the strong hint towards a Periodic Financial Report (RNF 2022-12-31), if the actual content were present, it would likely be 10-K (if annual) or IR (if interim). Since this is just the signature wrapper, and it's not an announcement (RPA), 'RNS' (General Regulatory Filings) is the safest classification for this technical artifact.
2023-03-11 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.