BIZTRAC BETA
Rental and operating of own or leased real estate

VATNEBRYN EIENDOM AS

Org. no. 995672820 Limited company (AS) Flesberg Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 334,000
Operating profit NOK 210,000
Equity NOK 1.1m
Incorporated 2010
Share capital NOK 100,000

VATNEBRYN EIENDOM AS is registered as a limited company in Flesberg, Buskerud with organisation number 995672820. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom og hva dermed står i forbindelse, samt ved kjøp av aksjer eller på annen måte delta i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 334,000 in revenue and NOK 210,000 in operating profit.

Key figures · 2024

Revenue
NOK 334,000
Operating profit
NOK 210,000
Equity
NOK 1.1m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns VATNEBRYN EIENDOM AS?

GEIR VATNEBRYN
VATNEBRYN EIENDOM AS
NOK 334,000 rev. · NOK 210,000 profit

VATNEBRYN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VATNEBRYN EIENDOM AS

Who owns VATNEBRYN EIENDOM AS?

GEIR VATNEBRYN is the largest registered owner, with 100.0%.

What is the revenue of VATNEBRYN EIENDOM AS?

VATNEBRYN EIENDOM AS had revenue of NOK 334,000 in 2024.

Who is the general manager of VATNEBRYN EIENDOM AS?

Geir Vatnebryn is registered as general manager of VATNEBRYN EIENDOM AS.

Where is VATNEBRYN EIENDOM AS based?

VATNEBRYN EIENDOM AS has its business address in Svene.

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.