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

GRØNLIHØGDA EIENDOM AS

Org. no. 936928277 Limited company (AS) Namsos Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 1.1m
Incorporated 2025
Share capital NOK 1.1m

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-12-18.

GRØNLIHØGDA EIENDOM AS is registered as a limited company in Namsos, Trøndelag with organisation number 936928277. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 1.1m, divided into 1120 shares. The company's stated purpose is: “Anskaffelse, drift, utvikling og forvaltning av faste eiendom, samt hva naturlig hører sammen med dette. Kjøp og salg av byggtjenester, samt hva naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns GRØNLIHØGDA EIENDOM AS?

GRØNLIHØGDA EIENDOM AS
NOK 0 rev. · NOK 0 profit

GRØNLIHØGDA EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRØNLIHØGDA EIENDOM AS

Who owns GRØNLIHØGDA EIENDOM AS?

EFOR AS is the largest registered owner, with 46.4%.

What is the revenue of GRØNLIHØGDA EIENDOM AS?

GRØNLIHØGDA EIENDOM AS had revenue of NOK 0 in 2025.

Where is GRØNLIHØGDA EIENDOM AS based?

GRØNLIHØGDA EIENDOM AS has its business address in Spillum.

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.