BIZTRAC BETA
Rental and operating of own or leased real estate

GRENSESVINGEN 7 EIENDOM AS

Org. no. 987767537 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 56.3m
Operating profit NOK 35.3m
Equity NOK 273.6m
Incorporated 2005
Share capital NOK 1.4m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRENSESVINGEN 7 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 987767537. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.4m, divided into 13500 shares. The company's stated purpose is: “Erverve, utvikle og drive faste eiendommer samt enhver annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 56.3m in revenue and NOK 35.3m in operating profit.

Key figures · 2024

Revenue
NOK 56.3m
Operating profit
NOK 35.3m
Equity
NOK 273.6m
Est. value
NOK 261.6m

Financial health · 2024

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

Who owns GRENSESVINGEN 7 EIENDOM AS?

HARDANGERJØKULEN AS
GRENSESVINGEN 7 EIENDOM AS
NOK 56.3m rev. · NOK 35.3m profit

GRENSESVINGEN 7 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRENSESVINGEN 7 EIENDOM AS

Who owns GRENSESVINGEN 7 EIENDOM AS?

HARDANGERJØKULEN AS is the largest registered owner, with 100.0%.

What is the revenue of GRENSESVINGEN 7 EIENDOM AS?

GRENSESVINGEN 7 EIENDOM AS had revenue of NOK 56.3m in 2024.

Where is GRENSESVINGEN 7 EIENDOM AS based?

GRENSESVINGEN 7 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 15.06.2026.

Report a problem

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