BIZTRAC BETA
Floor and wall covering

MIKAEL HÅNDVERKER AS

Org. no. 920125972 Limited company (AS) Aurskog-Høland Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 433,000
Equity NOK 140,000
Incorporated 2017
Share capital NOK 30,000

MIKAEL HÅNDVERKER AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 920125972. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å utføgre et bredt spektrum av byggearbeider, flislegging, gulvlegging, montering av vinduer og dører, maling; restuarering av klassiske biler og salg av deler for dem, renholdstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 433,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 433,000
Equity
NOK 140,000
Est. value
NOK 815,000

Financial health · 2025

Liquidity
3.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.4%
Weak
Equity as a share of total capital

Who owns MIKAEL HÅNDVERKER AS?

MICHAL PIOTR BIERNAT
MIKAEL HÅNDVERKER AS
NOK 4.3m rev. · NOK 433,000 profit

MIKAEL HÅNDVERKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIKAEL HÅNDVERKER AS

Who owns MIKAEL HÅNDVERKER AS?

MICHAL PIOTR BIERNAT is the largest registered owner, with 100.0%.

What is the revenue of MIKAEL HÅNDVERKER AS?

MIKAEL HÅNDVERKER AS had revenue of NOK 4.3m in 2025.

Who is the general manager of MIKAEL HÅNDVERKER AS?

Michal Piotr Biernat is registered as general manager of MIKAEL HÅNDVERKER AS.

Where is MIKAEL HÅNDVERKER AS based?

MIKAEL HÅNDVERKER AS has its business address in Aurskog.

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.