BIZTRAC BETA
Site preparation

BM ANLEGG AS

Org. no. 998824842 Limited company (AS) Vennesla Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 9.2m
Operating profit NOK −653,000
Equity NOK −925,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

BM ANLEGG AS is registered as a limited company in Vennesla, Agder with organisation number 998824842. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenør, herunder delta i andre selskaper som aksjeeier eller ansvarlig deltaker med likeartet formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.2m in revenue and NOK −653,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.2m
Operating profit
NOK −653,000
Equity
NOK −925,000

Financial health · 2024

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

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

Who owns BM ANLEGG AS?

VIDAR BIRKEDAL
BM ANLEGG AS
NOK 9.2m rev. · NOK −653,000 profit

BM ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BM ANLEGG AS

Who owns BM ANLEGG AS?

VIDAR BIRKEDAL is the largest registered owner, with 100.0%.

What is the revenue of BM ANLEGG AS?

BM ANLEGG AS had revenue of NOK 9.2m in 2024.

Who is the general manager of BM ANLEGG AS?

Kristoffer Cassidy Thomassen is registered as general manager of BM ANLEGG AS.

Where is BM ANLEGG AS based?

BM ANLEGG AS has its business address in Vennesla.

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.