BIZTRAC BETA
Repair and maintenance of electrical equipment

MICROFABRIKK AS

Org. no. 917968667 Limited company (AS) Larvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 823,000
Operating profit NOK 83,000
Equity NOK 96,000
Incorporated 2016
Share capital NOK 30,000

MICROFABRIKK AS is registered as a limited company in Larvik, Vestfold with organisation number 917968667. The business is classified under repair and maintenance of electrical equipment (NACE 33.140). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Reparasjon og design av elektroniske enheter. 3d printing og IT tjenester. Kjøp og salg av brukte varer og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 823,000 in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 823,000
Operating profit
NOK 83,000
Equity
NOK 96,000
Est. value
NOK 365,000

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MICROFABRIKK AS?

KRZYSZTOF OSTROWSKI
MICROFABRIKK AS
NOK 823,000 rev. · NOK 83,000 profit

MICROFABRIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MICROFABRIKK AS

Who owns MICROFABRIKK AS?

KRZYSZTOF OSTROWSKI is the largest registered owner, with 100.0%.

What is the revenue of MICROFABRIKK AS?

MICROFABRIKK AS had revenue of NOK 823,000 in 2025.

Who is the general manager of MICROFABRIKK AS?

Krzysztof Ostrowski is registered as general manager of MICROFABRIKK AS.

Where is MICROFABRIKK AS based?

MICROFABRIKK AS has its business address in Larvik.

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.