BIZTRAC BETA
Rental and operating of own or leased real estate

BERGØY EIENDOM AS

Org. no. 928423247 Limited company (AS) Halden Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 454,000
Operating profit NOK 401,000
Equity NOK 1.7m
Incorporated 2021
Share capital NOK 675,000

BERGØY EIENDOM AS is registered as a limited company in Halden, Østfold with organisation number 928423247. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 675,000, divided into 675000 shares. The company's stated purpose is: “Investering i eiendom for drift og utleie og alt annet som naturlig faller sammen med dette, herunder å delta i selskaper med liknende virksomhet, kjøp og salg av aksjer eller eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 454,000 in revenue and NOK 401,000 in operating profit.

Key figures · 2025

Revenue
NOK 454,000
Operating profit
NOK 401,000
Equity
NOK 1.7m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns BERGØY EIENDOM AS?

JEMS CAPITAL AS
BERGØY EIENDOM AS
NOK 454,000 rev. · NOK 401,000 profit

BERGØY EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BERGØY EIENDOM AS own?

BERGØY EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BERGØY EIENDOM AS

Who owns BERGØY EIENDOM AS?

JEMS CAPITAL AS is the largest registered owner, with 50.0%.

What is the revenue of BERGØY EIENDOM AS?

BERGØY EIENDOM AS had revenue of NOK 454,000 in 2025.

Where is BERGØY EIENDOM AS based?

BERGØY EIENDOM AS has its business address in Halden.

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.