biztrac. BETA
COMPANY REGISTER PROFILE
932763257 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HÅGEBERG EIENDOM AS

Org. no. 932763257 Limited company (AS) Oslo Incorporated 2023 Active
Revenue 2025 NOK 38,000
Operating profit NOK −10,000
Equity NOK −45,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−45k kr).

HÅGEBERG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 932763257. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i eiendom og annet som hører naturlig til dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 38,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 38,000
Operating profit
NOK −10,000
▲ +35 %
Equity
NOK −45,000
▼ −644 %

Financial health · 2025

Liquidity
5.90
Very good
Current assets ÷ current liabilities
Profitability
-0.5%
Not satisfactory
Return on total assets
Solidity
-1.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HÅGEBERG EIENDOM AS?

HÅGEBERG EIENDOM AS
NOK 38,000 rev. · NOK −10,000 profit

HÅGEBERG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HÅGEBERG EIENDOM AS

Who owns HÅGEBERG EIENDOM AS?

Kari Ingeborg Stensrud is the largest registered owner, with 50.0%.

What is the revenue of HÅGEBERG EIENDOM AS?

HÅGEBERG EIENDOM AS had revenue of NOK 38,000 in 2025.

Where is HÅGEBERG EIENDOM AS based?

HÅGEBERG EIENDOM 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.