BIZTRAC BETA
Roofing activities

LAPPEBAKKEN AS

Org. no. 919764961 Limited company (AS) Modum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 60,000
Operating profit NOK −33,000
Equity NOK −241,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

LAPPEBAKKEN AS is registered as a limited company in Modum, Buskerud with organisation number 919764961. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Taktekking og blikkenslagerarbeid og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 60,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2024

Revenue
NOK 60,000
Operating profit
NOK −33,000
Equity
NOK −241,000

Financial health · 2025

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

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

Who owns LAPPEBAKKEN AS?

Jon-Åge Lappebakken
LAPPEBAKKEN AS
NOK 60,000 rev. · NOK −33,000 profit

LAPPEBAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAPPEBAKKEN AS

Who owns LAPPEBAKKEN AS?

Jon-Åge Lappebakken is the largest registered owner, with 100.0%.

What is the revenue of LAPPEBAKKEN AS?

LAPPEBAKKEN AS had revenue of NOK 60,000 in 2024.

Who is the general manager of LAPPEBAKKEN AS?

Jon-Åge Lappebakken is registered as general manager of LAPPEBAKKEN AS.

Where is LAPPEBAKKEN AS based?

LAPPEBAKKEN AS has its business address in Åmot.

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.