Skip to main content
Mo-BRUK S.A. logo

Mo-BRUK S.A. — Investor Relations & Filings

Ticker · MBR ISIN · PLMOBRK00013 LEI · 259400SF7M4PJCF1PN49 WAR Water supply; sewerage, waste management and remediation activities
Filings indexed 683 across all filing types
Latest filing 2024-04-25 Regulatory Filings
Country PL Poland
Listing WAR MBR

About Mo-BRUK S.A.

https://mobruk.pl/

Mo-BRUK S.A. is a specialized waste management company focused on processing industrial, hazardous, and select municipal waste. The company's core activities are organized into three main segments: the solidification and stabilization of inorganic waste, the production of alternative fuels from waste, and the incineration of hazardous and medical waste. It offers comprehensive waste management solutions, from collection and transport to final disposal and recovery. A key aspect of its business model is the transformation of waste into usable products, such as artificial aggregates, contributing to a circular economy. The company is capable of processing a wide variety of waste types, including those from thermal treatment facilities.

Recent filings

Filing Released Lang Actions
Sprawozdanie niezależnego biegłego rewidenta z badania rocznego sprawozdania finansowego za 2023 r.
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structures related to digital signatures (Signature, SignedInfo, SignatureValue, KeyInfo, etc.). This structure is typical of digitally signed regulatory filings or official documents submitted electronically, often in formats like XML or XBRL, rather than the content of a standard report (like 10-K, IR, or ER). Key indicators are: 1. Presence of XML Digital Signature elements (ds:Signature, ds:SignedInfo, ds:SignatureValue). 2. References to specific files being signed, such as "MBR_SzB_JSF_MSR_2023-12-31_PL.xhtml". The 'MSR' often suggests a Management/Statutory Report, and the date '2023-12-31' indicates a year-end period. 3. The presence of a certificate issued to 'Certum QCA 2017' and references to Polish entities ('PL', 'Warszawa', 'Płock'). Since the document is not the content of the report itself (it's the signature block), and it is a formal, digitally signed submission, it fits best under the general category for regulatory filings that don't have a more specific code, or potentially an Audit Report (AR) if the signed file name implies an audit/statutory report. However, without the actual content, and given the structure is purely metadata/security, the most appropriate general classification for a formal, signed submission that isn't explicitly an ER, 10-K, or IR is the fallback category for regulatory filings. Given the file name reference 'MBR_SzB_JSF_MSR_2023-12-31_PL.xhtml', MSR often stands for Management/Statutory Report. If this were the report itself, it might be classified as IR (Interim Report) or 10-K (Annual Report), but since this is just the signature wrapper, RNS (Regulatory Filings) is the safest classification for the wrapper document itself, as per Rule 2 (Menu vs Meal rule, although this is a signature wrapper, not an announcement of a report). If we assume the signed document is a statutory report for the year-end 2023, it leans towards 10-K content, but the document *provided* is the signature block.
2024-04-25 Polish
Sprawozdanie niezależnego biegłego rewidenta z badania rocznego sprawozdania finansowego za 2023 r.
Audit Report / Information Classification · 95% confidence The document text provided is extremely short (relative to the 768k character total length, but the visible text is minimal and appears to be HTML/CSS boilerplate from a PDF conversion tool ('pdf2htmlEX'). The title tag reads 'Raport', which is Polish for 'Report'. Given the context of financial documents, 'Raport' often refers to a periodic financial report (like an Interim Report or Annual Report). However, the actual content is missing, replaced by styling information. Since the document length is very large (768,816 chars), it suggests a comprehensive document, not just a short announcement. The title 'Raport' is generic. Without specific keywords like '10-K', 'Q3', 'Balance Sheet', or 'Earnings', and given the Polish language context, the most appropriate classification for a comprehensive, non-SEC-specific 'Report' that isn't explicitly an Annual Report (10-K) or an Interim Report (IR) is difficult. However, if we assume 'Raport' refers to a standard, comprehensive financial filing, 'IR' (Interim/Quarterly Report) or 'AR' (Audit Report/Information) are possibilities. Given the lack of specific content confirming it's quarterly or audited, and the generic nature, I will lean towards the most common comprehensive report type that isn't the 10-K, which is the Interim Report (IR), or the generic Audit Report (AR) if it's an annual filing without the full 10-K structure. Since the document is very long, it is likely a full report, not an announcement (RPA/RNS). Given the ambiguity, and the Polish title 'Raport', I will classify it as an Interim Report (IR) as it covers a defined period, which is a common structure for such reports, while acknowledging the high uncertainty due to missing content. FY 2023
2024-04-25 Polish
Oświadczenie Rady Nadzorczej
Regulatory Filings Classification · 95% confidence The document text provided is primarily composed of HTML structure, CSS styles, and font data, indicating it is a conversion artifact (likely from a PDF using pdf2htmlEX) rather than the content of a standard financial filing. The title tag contains 'Oswiadczenie_RN_2023-12-31_pl.xhtml'. 'Oswiadczenie' is Polish for 'Statement' or 'Declaration'. The presence of 'RN' suggests a regulatory notice or statement. Given the highly technical, non-content nature of the provided text (it's the underlying structure/styling), and the Polish title suggesting a 'Statement/Declaration' related to a date (2023-12-31), the most appropriate general category for a regulatory statement that isn't a specific report (like 10-K or IR) is the fallback category, Regulatory Filings (RNS). The document length is very large (over 2 million characters), suggesting it contains substantial content, but the provided snippet is only the header/styling, which is misleading. Assuming the full document contains a regulatory statement, RNS is the best fit among the options, as it serves as a general regulatory announcement category.
2024-04-25 Polish
Sprawozdanie Zarządu z działalności za 2023 r. - jednostkowe
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 digitally signed regulatory filings or documents where integrity and authenticity must be verified, often found within XBRL or XML-based submissions to regulatory bodies like the SEC or European equivalents. The presence of references to 'SSZzD_GK_MBR_2023-12-31_pl.xhtml' and the overall structure strongly suggest this is the signature block of a formal filing. Since the content is purely metadata/signature and not the substantive report itself (like a 10-K or IR), and given the context of corporate filings, the most appropriate general classification for a document primarily composed of regulatory signature data, especially when the underlying document type is obscured by the signature wrapper, is the general 'Regulatory Filings' fallback category (RNS). The document length (38120 chars) is substantial, suggesting it wraps a full report, but since we only see the signatures, RNS is the safest classification for the wrapper itself, unless specific content points elsewhere. However, since the reference URI points to an XHTML file dated 2023-12-31, this is likely the signature page of an Annual Report (10-K) or an Interim Report (IR) filed in XBRL format. Given the lack of actual financial content, RNS is the best fit for the signature wrapper itself, as per Rule 2.
2024-04-25 Polish
Sprawozdanie Zarządu z działalności za 2023 r. - jednostkowe
Board/Management Information Classification · 95% confidence The document text provided is primarily composed of HTML structure, CSS styling, and metadata related to the conversion of a PDF file into an XHTML format (indicated by tags like 'html', 'head', 'title', and extensive CSS definitions for page layout and fonts). The title of the document is 'SSZzD_GK_MBR_2023-12-31_pl.xhtml'. The presence of a date (2023-12-31) and the structure suggest this is a container or wrapper for a financial report, but the content itself is not the report narrative or structured data. Given the extremely large character count (7.7 million characters), it is highly likely that this is the full content of a comprehensive report that has been converted to HTML/XML, rather than a short announcement. However, the classification definitions require identifying the *type* of report. Since the content is the raw, converted structure and lacks explicit headers like '10-K', 'Annual Report', or 'Interim Report', and the document length is massive, it strongly suggests a comprehensive filing. If we look closely at the decoded text within the document (which is heavily obfuscated by font data and CSS), there are no clear keywords pointing to 10-K, IR, or ER. The file name 'SSZzD_GK_MBR_2023-12-31_pl.xhtml' is cryptic. In the absence of clear content keywords, and given the massive size suggesting a full report, the most appropriate general category for a comprehensive, large, regulatory-style document that doesn't fit a specific narrative type is often the Annual Report (10-K) or Interim Report (IR). Since the date is year-end (12-31), it leans towards an Annual Report. However, the document is presented as an HTML/XML conversion artifact, not the clean report itself. If this were a standard filing feed, this artifact would typically accompany the primary filing. Since I must choose one of the defined types, and the size implies a major filing, I will tentatively classify it as the most comprehensive annual filing, the 10-K, while acknowledging the classification is based on size/date inference rather than explicit content keywords. Revisiting the definitions: 10-K is the 'Official yearly report'. Given the 12-31 date, this is the most likely candidate for the underlying document being represented by this large artifact.
2024-04-25 Polish
Sprawozdanie finansowe jednostkowe za 2023 r.
Audit Report / Information Classification · 95% confidence The document text provided consists almost entirely of XML digital signature blocks (specifically XAdES/XML-DSig structures) used to verify the authenticity and integrity of a file. The key piece of information is found within the `DataObjectFormat` description inside the signature properties: `Content-Disposition: filename="SF_MO-BRUK_S_A_MSSF_2023-12-31_pl.xhtml"`. The filename strongly suggests a document related to financial statements or reports ending in 'SF' (Statement/Supplement/Financial) for the period ending 2023-12-31. Since the document itself is just the signature wrapper and not the content of the financial report, and given the context of corporate filings, this structure is typical of a regulatory filing that has been digitally signed for submission or publication. The presence of multiple signatures and the XML structure points towards a formal submission. Since the actual content (like a 10-K or IR) is not present, and this is a signed artifact, the most appropriate classification is the general fallback for formal regulatory submissions, 'RNS' (Regulatory Filings), or potentially 'XLSX' if 'SF' implies a data supplement, but 'RNS' is safer for a signed XML wrapper. However, looking closely at the definitions, the filename contains 'MSSF' which often relates to International Financial Reporting Standards (IFRS) or similar statutory reporting, and the document length is substantial (48k chars), suggesting it might be the report itself wrapped in signatures, or a very detailed signed filing. Given the structure is a signed XML document, and the filename suggests a financial statement/supplement ('SF_..._MSSF_...'), this is a formal regulatory submission. If it were a short announcement *about* the filing, it would be RPA/RNS. Since the document is large and contains the signature structure for the actual file (referenced by URI), it is likely the filing itself, but the content shown is only the signature. In cases where the content is obscured by signatures but the metadata points to a specific report type, we must rely on the filename. 'SF' often stands for 'Statutory Filing' or 'Financial Supplement'. Given the options, and the fact that the content is a signed artifact referencing a financial document, 'RNS' (General Regulatory Filings) is the best fit for the wrapper, or if we assume the wrapped content is the primary document, it's hard to pin down without seeing the content. Given the 'MENU VS MEAL' rule, if this were just an announcement, it would be RPA. Since it contains the full signature block for the file, it is the filing itself, but the classification options don't perfectly match a signed XML filing wrapper. We default to RNS as the most general regulatory category for signed submissions that aren't explicitly 10-K or IR. Revisiting the filename: 'SF_MO-BRUK_S_A_MSSF_2023-12-31_pl.xhtml'. This looks like a statutory financial statement (MSSF = Polish equivalent of IFRS/MS-IFRS). This strongly suggests an Interim Report (IR) or Annual Report (10-K). Since it's for a full year (2023-12-31), it leans towards 10-K, but Polish companies often file under local regulations which might map better to IR (Interim/Annual Report) or AR (Audit Report). Given the ambiguity and the fact that the content is just the signature, RNS remains the safest classification for the *wrapper* document itself, but if we classify the *intended* document, it's a comprehensive annual report. Let's assume the intent is to classify the underlying document referenced by the signature, which is a full-year financial statement. This aligns best with '10-K' (Annual Report) or 'AR' (Audit Report/Information). Since it's a full-year statement, 10-K is the closest US equivalent for a comprehensive annual filing. However, without confirmation of the content, RNS is the classification for the *container*. Given the high confidence required, and the document being a signed XML structure, it is a formal regulatory submission. We choose RNS as the most appropriate category for a signed regulatory artifact that isn't clearly an ER or IR based on the visible text. *Self-Correction based on typical filing patterns*: Documents that are primarily XML signatures often represent the final submission package. If the underlying document is a full-year financial statement, 10-K is the best fit for comprehensive annual data, even if the wrapper is signed. However, the visible text is *only* the signature. I will stick to RNS as the classification for the visible document type (a signed artifact/submission wrapper), as per the 'MENU VS MEAL' rule applied to the visible text structure. *Final Decision*: The document is a digitally signed file wrapper. This is a regulatory filing artifact. Code: RNS. FY 2023
2024-04-25 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.