BIZTRAC BETA
Rental and operating of own or leased real estate

BERGSENG-JOSTAD EIENDOM AS

Org. no. 912893464 Limited company (AS) Gjøvik Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 150,000
Operating profit NOK 39,000
Equity NOK 409,000
Incorporated 2013
Share capital NOK 150,000

BERGSENG-JOSTAD EIENDOM AS is registered as a limited company in Gjøvik, Innlandet with organisation number 912893464. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Investere i eiendom, drive utleie og alt som hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 150,000 in revenue and NOK 39,000 in operating profit.

Key figures · 2024

Revenue
NOK 150,000
Operating profit
NOK 39,000
Equity
NOK 409,000
Est. value
NOK 334,000

Financial health · 2024

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.3%
Good
Equity as a share of total capital

Who owns BERGSENG-JOSTAD EIENDOM AS?

HARALD BERGSENG
BERGSENG-JOSTAD EIENDOM AS
NOK 150,000 rev. · NOK 39,000 profit

BERGSENG-JOSTAD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGSENG-JOSTAD EIENDOM AS

Who owns BERGSENG-JOSTAD EIENDOM AS?

HARALD BERGSENG is the largest registered owner, with 50.0%.

What is the revenue of BERGSENG-JOSTAD EIENDOM AS?

BERGSENG-JOSTAD EIENDOM AS had revenue of NOK 150,000 in 2024.

Who is the general manager of BERGSENG-JOSTAD EIENDOM AS?

Haakon Martin Jostad Jacobsen is registered as general manager of BERGSENG-JOSTAD EIENDOM AS.

Where is BERGSENG-JOSTAD EIENDOM AS based?

BERGSENG-JOSTAD EIENDOM AS has its business address in Hunndalen.

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.