BIZTRAC BETA
Construction of residential and non-residential buildings

PLANKEMANN AS

Org. no. 929499107 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 268,000
Operating profit NOK −117,000
Equity NOK 692,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−117k kr).

PLANKEMANN AS is registered as a limited company in Asker, Akershus with organisation number 929499107. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive tømrer- og investeringsvirksomhet, herunder å investere i aksjer og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 268,000 in revenue and NOK −117,000 in operating profit.

Key figures · 2025

Revenue
NOK 268,000
Operating profit
NOK −117,000
Equity
NOK 692,000
Est. value
NOK 391,000

Financial health · 2025

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

Who owns PLANKEMANN AS?

FREDRIK MARTINSEN
PLANKEMANN AS
NOK 268,000 rev. · NOK −117,000 profit

PLANKEMANN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PLANKEMANN AS own?

PLANKEMANN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PLANKEMANN AS

Who owns PLANKEMANN AS?

FREDRIK MARTINSEN is the largest registered owner, with 100.0%.

What is the revenue of PLANKEMANN AS?

PLANKEMANN AS had revenue of NOK 268,000 in 2025.

Where is PLANKEMANN AS based?

PLANKEMANN AS has its business address in Nærsnes.

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.