BIZTRAC BETA
General medical practice activities

BERGSVEIN AS

Org. no. 993941050 Limited company (AS) Lillehammer Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 292,000
Operating profit NOK 100,000
Equity NOK 6.7m
Incorporated 2009
Share capital NOK 1.2m

BERGSVEIN AS is registered as a limited company in Lillehammer, Innlandet with organisation number 993941050. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2009. Registered share capital is NOK 1.2m, divided into 1100 shares. The company's stated purpose is: “Investeringer i aksjer og verdipapirer, selskaper, selskapsandeler og fast eiendom samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 292,000 in revenue and NOK 100,000 in operating profit.

Key figures · 2025

Revenue
NOK 292,000
Operating profit
NOK 100,000
Equity
NOK 6.7m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns BERGSVEIN AS?

ARE BERGSVEIN TVINNEREIM
BERGSVEIN AS
NOK 292,000 rev. · NOK 100,000 profit

BERGSVEIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERGSVEIN AS own?

BERGSVEIN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BERGSVEIN AS

Who owns BERGSVEIN AS?

ARE BERGSVEIN TVINNEREIM is the largest registered owner, with 100.0%.

What is the revenue of BERGSVEIN AS?

BERGSVEIN AS had revenue of NOK 292,000 in 2025.

Who is the general manager of BERGSVEIN AS?

Are Bergsvein Tvinnereim is registered as general manager of BERGSVEIN AS.

Where is BERGSVEIN AS based?

BERGSVEIN AS has its business address in Lillehammer.

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.