BIZTRAC BETA
Rental and operating of own or leased real estate

HOBERGVN. 147 OTTESTAD AS

Org. no. 997838793 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK 2.7m
Equity NOK 11.0m
Incorporated 2011
Share capital NOK 1.2m

HOBERGVN. 147 OTTESTAD AS is registered as a limited company in Oslo, Oslo with organisation number 997838793. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Utvikle, eie og forvalte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK 2.7m in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK 2.7m
Equity
NOK 11.0m
Est. value
NOK 12.0m

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.4%
Good
Equity as a share of total capital

Who owns HOBERGVN. 147 OTTESTAD AS?

NG EIENDOM INNLAND AS
HOBERGVN. 147 OTTESTAD AS
NOK 4.0m rev. · NOK 2.7m profit

HOBERGVN. 147 OTTESTAD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HOBERGVN. 147 OTTESTAD AS er morselskap for 249 datterselskaper:

Frequently asked questions about HOBERGVN. 147 OTTESTAD AS

Who owns HOBERGVN. 147 OTTESTAD AS?

NG EIENDOM INNLAND AS is the largest registered owner, with 100.0%.

What is the revenue of HOBERGVN. 147 OTTESTAD AS?

HOBERGVN. 147 OTTESTAD AS had revenue of NOK 4.0m in 2024.

Who is the general manager of HOBERGVN. 147 OTTESTAD AS?

Paul Eivind Ramberg is registered as general manager of HOBERGVN. 147 OTTESTAD AS.

Where is HOBERGVN. 147 OTTESTAD AS based?

HOBERGVN. 147 OTTESTAD AS has its business address in Oslo.

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.