BIZTRAC BETA
Masonry and bricklaying activities

MINDALEN STEINANLEGG AS

Org. no. 822949002 Limited company (AS) Midt-Telemark Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 357,000
Equity NOK 514,000
Incorporated 2019
Employees 5
Share capital NOK 70,000

MINDALEN STEINANLEGG AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 822949002. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Steinlegging og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 357,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 357,000
Equity
NOK 514,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.7%
Very good
Equity as a share of total capital

Who owns MINDALEN STEINANLEGG AS?

KATARZYNA MATAREWICZ MINDALEN
MINDALEN STEINANLEGG AS
NOK 3.5m rev. · NOK 357,000 profit

MINDALEN STEINANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MINDALEN STEINANLEGG AS

Who owns MINDALEN STEINANLEGG AS?

KATARZYNA MATAREWICZ MINDALEN is the largest registered owner, with 100.0%.

What is the revenue of MINDALEN STEINANLEGG AS?

MINDALEN STEINANLEGG AS had revenue of NOK 3.5m in 2025.

Who is the general manager of MINDALEN STEINANLEGG AS?

Katarzyna Matarewicz Mindalen is registered as general manager of MINDALEN STEINANLEGG AS.

Where is MINDALEN STEINANLEGG AS based?

MINDALEN STEINANLEGG AS has its business address in Bø I Telemark.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.