BIZTRAC BETA
Rental and operating of own or leased real estate

JÆGERBAKKEN 37 AS

Org. no. 994865188 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 728,000
Operating profit NOK 499,000
Equity NOK 823,000
Incorporated 2009
Share capital NOK 100,000

JÆGERBAKKEN 37 AS is registered as a limited company in Bergen, Vestland with organisation number 994865188. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Eiendomsutvikling, oppføring av bygninger, eiendomsbesittelse, drift av fast eiendom samt øvrige forhold som har sammenheng med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 728,000 in revenue and NOK 499,000 in operating profit.

Key figures · 2025

Revenue
NOK 728,000
Operating profit
NOK 499,000
Equity
NOK 823,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.8%
Satisfactory
Equity as a share of total capital

Who owns JÆGERBAKKEN 37 AS?

OLE KRISTIAN HAVRE
JÆGERBAKKEN 37 AS
NOK 728,000 rev. · NOK 499,000 profit

JÆGERBAKKEN 37 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JÆGERBAKKEN 37 AS

Who owns JÆGERBAKKEN 37 AS?

OLE KRISTIAN HAVRE is the largest registered owner, with 33.3%.

What is the revenue of JÆGERBAKKEN 37 AS?

JÆGERBAKKEN 37 AS had revenue of NOK 728,000 in 2025.

Who is the general manager of JÆGERBAKKEN 37 AS?

Ole Kristian Havre is registered as general manager of JÆGERBAKKEN 37 AS.

Where is JÆGERBAKKEN 37 AS based?

JÆGERBAKKEN 37 AS has its business address in Søreidgrend.

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.