BIZTRAC BETA
COMPANY REGISTER PROFILE
914172144 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

PLANLEGG.NO AS

Org. no. 914172144 Limited company (AS) Kongsberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −167,000
Incorporated 2014
Share capital NOK 40,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−167k kr).

PLANLEGG.NO AS is registered as a limited company in Kongsberg, Buskerud with organisation number 914172144. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2014. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Investere i aksjer og andeler i andre selskaper og i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −167,000

Financial health · 2025

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

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

Who owns PLANLEGG.NO AS?

PLANLEGG.NO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PLANLEGG.NO AS own?

PLANLEGG.NO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PLANLEGG.NO AS

Who owns PLANLEGG.NO AS?

BENTE BJERKE HOGGANVIK is the largest registered owner, with 70.0%.

What is the revenue of PLANLEGG.NO AS?

PLANLEGG.NO AS had revenue of NOK 0 in 2025.

Who is the general manager of PLANLEGG.NO AS?

Bente Bjerke Hogganvik is registered as general manager of PLANLEGG.NO AS.

Where is PLANLEGG.NO AS based?

PLANLEGG.NO AS has its business address in Kongsberg.

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

Report a problem

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