BIZTRAC BETA
Site preparation

BLEFJELL ENTREPRENØR AS

Org. no. 922597960 Limited company (AS) Flesberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 2.3m
Equity NOK 5.5m
Incorporated 2019
Share capital NOK 50,000

BLEFJELL ENTREPRENØR AS is registered as a limited company in Flesberg, Buskerud with organisation number 922597960. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Graving, transport, brøyting, oppføring av hytter og grunnarbeid, samt øvrig entreprenørvirksomhet og utleie av fast eiendom. Selskapet skal videre ha anledning til å delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 2.3m
Equity
NOK 5.5m
Est. value
NOK 10.0m

Financial health · 2025

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

Who owns BLEFJELL ENTREPRENØR AS?

ANUND DRAMDAL BORGE
BLEFJELL ENTREPRENØR AS
NOK 6.9m rev. · NOK 2.3m profit

BLEFJELL ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLEFJELL ENTREPRENØR AS

Who owns BLEFJELL ENTREPRENØR AS?

ANUND DRAMDAL BORGE is the largest registered owner, with 100.0%.

What is the revenue of BLEFJELL ENTREPRENØR AS?

BLEFJELL ENTREPRENØR AS had revenue of NOK 6.9m in 2025.

Who is the general manager of BLEFJELL ENTREPRENØR AS?

Anund Dramdal Borge is registered as general manager of BLEFJELL ENTREPRENØR AS.

Where is BLEFJELL ENTREPRENØR AS based?

BLEFJELL ENTREPRENØR AS has its business address in Lampeland.

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.