BIZTRAC BETA
Technical testing and analysis

BJØRN E BERG AS

Org. no. 889068922 Limited company (AS) Østre Toten Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 1.1m
Equity NOK 13.9m
Incorporated 2005
Share capital NOK 100,000

BJØRN E BERG AS is registered as a limited company in Østre Toten, Innlandet with organisation number 889068922. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester innen miljøteknologi, miljøkjemi, miljørapporterinig, teknisk prøving og prøving samt annen sivilingeniør-virksomhet, kursvirksomhet, deltagelse og investering i andre selskaper, kjøp og salg av fast eiendom samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 1.1m
Equity
NOK 13.9m
Est. value
NOK 12.4m

Financial health · 2024

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

Who owns BJØRN E BERG AS?

BJØRN ERLING BERG
BJØRN E BERG AS
NOK 1.5m rev. · NOK 1.1m profit

BJØRN E BERG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJØRN E BERG AS

Who owns BJØRN E BERG AS?

BJØRN ERLING BERG is the largest registered owner, with 98.0%.

What is the revenue of BJØRN E BERG AS?

BJØRN E BERG AS had revenue of NOK 1.5m in 2024.

Who is the general manager of BJØRN E BERG AS?

Bjørn Erling Berg is registered as general manager of BJØRN E BERG AS.

Where is BJØRN E BERG AS based?

BJØRN E BERG AS has its business address in Lena.

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.