BIZTRAC BETA
Production of electricity from solar power

KRAPTER AS

Org. no. 932424800 Limited company (AS) Tynset Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −299,000
Equity NOK −226,000
Incorporated 2023
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−226k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−299k kr).

KRAPTER AS is registered as a limited company in Tynset, Innlandet with organisation number 932424800. The business is classified under production of electricity from solar power (NACE 35.123). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikle, bygge og drifte bakkemonterte solparker, herunder tjenester som entreprenør og totalentreprenør.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −299,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −299,000
Equity
NOK −226,000

Financial health · 2024

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

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

Who owns KRAPTER AS?

ØSTA INVEST AS
KRAPTER AS
NOK 1.0m rev. · NOK −299,000 profit

KRAPTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRAPTER AS

Who owns KRAPTER AS?

ØSTA INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of KRAPTER AS?

KRAPTER AS had revenue of NOK 1.0m in 2024.

Who is the general manager of KRAPTER AS?

Roar Tangen is registered as general manager of KRAPTER AS.

Where is KRAPTER AS based?

KRAPTER AS has its business address in Tynset.

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.