BIZTRAC BETA
Motion picture, video and television programme production activities

PLAN C AS

Org. no. 820177592 Limited company (AS) Kongsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 64,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

PLAN C AS is registered as a limited company in Kongsberg, Buskerud with organisation number 820177592. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Holdingsselskap. Eierskap og investering i nye og eksisterende selskaper, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 64,000
Est. value
NOK 116,000

Financial health · 2025

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

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

Who owns PLAN C AS?

BJØRN HELGE ISAKSEN
PLAN C AS
NOK 0 rev. · NOK −14,000 profit

PLAN C AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PLAN C AS own?

PLAN C AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PLAN C AS

Who owns PLAN C AS?

BJØRN HELGE ISAKSEN is the largest registered owner, with 60.0%.

What is the revenue of PLAN C AS?

PLAN C AS had revenue of NOK 0 in 2025.

Where is PLAN C AS based?

PLAN C 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 15.06.2026.

Report a problem

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