biztrac. BETA
COMPANY REGISTER PROFILE
993956198 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

VARHOLM EIENDOM AS

Org. no. 993956198 Limited company (AS) Bergen Incorporated 2009 Active
Revenue 2025 NOK 51,000
Operating profit NOK −459,000
Equity NOK 325,000
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−459k kr).

VARHOLM EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 993956198. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 51,000 in revenue and NOK −459,000 in operating profit.

Key figures · 2025

Revenue
NOK 51,000
Operating profit
NOK −459,000
▼ −3075 %
Equity
NOK 325,000
▲ +436 %
Est. value
NOK 298,000

Financial health · 2025

Liquidity
9.41
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
26.4%
Good
Equity as a share of total capital

Who owns VARHOLM EIENDOM AS?

VARHOLM EIENDOM AS
NOK 51,000 rev. · NOK −459,000 profit

VARHOLM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VARHOLM EIENDOM AS

Who owns VARHOLM EIENDOM AS?

BEFAS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VARHOLM EIENDOM AS?

VARHOLM EIENDOM AS had revenue of NOK 51,000 in 2025.

Who is the general manager of VARHOLM EIENDOM AS?

Ingri Lem Isdal is registered as general manager of VARHOLM EIENDOM AS.

Where is VARHOLM EIENDOM AS based?

VARHOLM EIENDOM AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.