Skip to main content
Megaron S.A. logo

Megaron S.A. — Investor Relations & Filings

Ticker · MEG ISIN · PLMGRON00016 LEI · 259400RUBJNWTQZ0ZC88 WAR Manufacturing
Filings indexed 582 across all filing types
Latest filing 2024-04-25 Regulatory Filings
Country PL Poland
Listing WAR MEG

About Megaron S.A.

https://megaron.com.pl/

Megaron S.A. is a manufacturer of construction chemicals and building materials specializing in products for interior finishing works, repairs, and construction. The company's product portfolio includes a range of ready-to-use and dry-mix compounds such as gypsum plasters, finishing putties, and specialized masses for joining drywall panels. Megaron also produces professional tile adhesives, including traditional cementitious and modern dispersion-based formulas. Other key products include a flexible, liquid roofing membrane used for both protective and decorative coatings. The company offers solutions for both professional contractors and the DIY market, focusing on high-quality mineral mixtures and polymer-based materials for various construction applications.

Recent filings

Filing Released Lang Actions
PISMO PREZESA ZARZĄDU - PODPIS
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structures related to digital signatures (Signature, SignedInfo, DigestValue, X509Data, etc.). This format is characteristic of digitally signed electronic documents, often used for regulatory filings or official correspondence where authenticity and integrity must be verified. Crucially, the document contains a reference to a file named "Pismo_Prezesa_Z_2023_2024-04-23_pl.xhtml" and a signing time of '2024-04-23T12:27:56Z'. The term 'Pismo Prezesa' translates from Polish to 'Letter from the President' or 'President's Correspondence'. Given the content is the signature block itself, and not the content of the letter/document it is signing, this strongly suggests the document is an official communication or filing that has been digitally signed. Since it is a specific piece of correspondence ('Pismo Prezesa') rather than a standard periodic report (10-K, IR, ER), and it is not a transcript (CT) or a general presentation (IP), the most appropriate classification is a general Regulatory Filing (RNS), which serves as a fallback for specific official correspondence that doesn't fit other categories, or potentially a Legal/Regulatory correspondence if the content implied a legal matter, but 'RNS' is the best fit for an official, signed, non-standard report communication.
2024-04-25 Polish
PISMO PREZESA ZARZĄDU
Management Reports Classification · 95% confidence The document text provided is extremely short (relative to the 15000 character truncation limit, and the total length of 140140 chars suggests a large document) and appears to be the raw HTML/CSS structure generated by a PDF conversion tool (pdf2htmlEX). The title tag is simply 'Raport' (Report in several languages). Crucially, there is no discernible content, financial figures, regulatory headers (like 10-K, AR, ER), or specific reporting periods that would allow classification into a specific financial filing type (10-K, IR, ER, etc.). Given the lack of substantive content and the nature of the text being conversion artifacts, this document cannot be classified as a specific financial report. It is most likely a placeholder or a document where the actual content failed to render or was not captured correctly, falling into the general regulatory/miscellaneous category, or perhaps an internal report (IR). However, since the text is almost entirely metadata/styling, and no specific report type is identifiable, the most appropriate fallback is the general Regulatory Filings category (RNS), as it covers miscellaneous or unclassifiable documents, although the confidence is low due to the lack of content.
2024-04-25 Polish
INFORMACJA ZARZĄDU DOTYCZACA WYBORU FIRMY AUDYTORSKIEJ - PODPISY
Audit Report / Information Classification · 95% confidence The document text consists almost entirely of XML structures related to digital signatures (xmlns:ds="http://www.w3.org/2000/09/xmldsig#" and xades elements). It contains references to files like "Inf_dot_wyb_aud_2023_2024-04-23_pl.xhtml" and includes signing times (e.g., 2024-04-23T10:19:45Z). The presence of the term 'aud' within the referenced filename, combined with the extensive digital signature block, strongly suggests this is metadata or a wrapper for an official document that has been signed for authenticity. Given the context of financial filings, a signed document often relates to an Audit Report (AR) or a formal regulatory filing. Since the content itself is just the signature block and not the substantive report content (like financial statements or management discussion), and the filename hints at an audit ('aud'), the most appropriate classification is Audit Report / Information (AR), assuming the signature block authenticates the underlying report. If this were merely an announcement of the report, it would be RPA, but the document length (37k chars) suggests it contains more than just a brief announcement, likely the signed artifact itself. FY 2023
2024-04-25 Polish
INFORMACJA ZARZĄDU DOTYCZACA WYBORU FIRMY AUDYTORSKIEJ
Audit Report / Information Classification · 95% confidence The document text provided is extremely short (relative to the 3 million character length indicated in metadata, but the visible text is just HTML/CSS boilerplate from a PDF conversion tool, with the title 'Raport'). Crucially, the document length is 3,093,538 characters, which is characteristic of a comprehensive report like a 10-K or a full Interim Report (IR). However, the visible text is only boilerplate and does not contain any financial data, management discussion, or regulatory headers. Given the massive size and the fact that the content is not visible, I must rely on the 'MENU VS MEAL' rule combined with the document size. A document this large is almost certainly a full report, not a short announcement. Since the content is not visible to determine if it's an Annual Report (10-K) or an Interim Report (IR), and there are no specific keywords, I will default to the most comprehensive annual filing type, 10-K, as the most likely candidate for a very large document, or use the fallback RNS if I cannot confirm the content type. Given the context of a premium database, a large document is usually a primary filing. Since I cannot confirm the content, I will use the fallback 'RNS' as the safest classification for an unreadable, large document, as it covers miscellaneous filings, or I will assume it is a full report. Given the ambiguity, I will check if 'Raport' suggests a specific type. 'Raport' is generic. I will classify it as a Regulatory Filing (RNS) because the actual content is inaccessible and only boilerplate is shown, suggesting this might be a wrapper or an unclassified filing, adhering to Rule 2 (though Rule 2 primarily targets short announcements, the lack of content in a large file is also problematic). However, if the document is truly 3MB, it is a full report. I will lean towards the most common large report, 10-K, but since I cannot verify, RNS is the safest fallback for an unclassifiable large file. Q3 2024
2024-04-25 Polish
OŚWIADCZENIE ZARZĄDU W SPRAWIE RZETELNOŚCI SPORZĄDZENIA SPRAWOZDANIA FINANSOWEGO - PODPISY
Regulatory Filings Classification · 95% confidence The document text consists almost entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, etc.). This structure is characteristic of documents that have been digitally signed for authenticity and integrity, often required for official regulatory submissions or legal documents in electronic format (like XBRL filings or specific regulatory reports). The presence of multiple signatures and the file name reference "Osw_dot_rzeteln_2023_2024-04-23_pl.xhtml" suggests this is the underlying data or a wrapper for a specific filing. Given the highly technical, non-narrative content (pure metadata/signature structure) and the document length (37k characters), it is not a standard narrative report (10-K, IR, ER) or a brief announcement (RPA, ER). Since it is a structured, signed document that doesn't fit the specific financial report types, the most appropriate fallback category for a complex, signed regulatory artifact is 'Regulatory Filings' (RNS).
2024-04-25 Polish
OŚWIADCZENIE ZARZĄDU W SPRAWIE RZETELNOŚCI SPORZĄDZENIA SPRAWOZDANIA FINANSOWEGO
Management Reports Classification · 95% confidence The document text provided is extremely short (truncated to 15000 chars, but the actual content is minimal HTML/CSS structure from a PDF conversion tool, indicated by tags like 'html', 'head', 'style', and CSS definitions). The title tag is 'Raport'. Crucially, the document length is very large (2,285,082 chars), suggesting the full document is substantial, but the provided snippet is just the boilerplate/metadata wrapper from the conversion process, not the substantive content of a financial report itself. Given the context of a large underlying document that has been converted from a PDF (implied by the CSS/HTML structure typical of pdf2htmlEX output) and the lack of any specific financial keywords (like '10-K', 'Earnings Release', 'Balance Sheet', etc.) in the visible text, this is most likely an announcement or wrapper for a larger filing. Since the text itself does not contain the content of a report but rather the structure of a rendered file, and it is not explicitly announcing the publication of a report (which would trigger RPA/RNS), the most appropriate classification for a generic, large, non-standardized document structure that doesn't fit other categories is the fallback, Regulatory Filings (RNS), or if we assume the underlying document is a comprehensive report that failed to render its content, we must rely on the structure. However, following Rule 2 (Menu vs Meal), if the text is just a wrapper, it points away from the actual report type. Since there is no clear indication of the content type (like an ER or 10-K), RNS is the safest fallback for an unclassifiable regulatory document structure.
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.