BIZTRAC BETA
Architectural activities

GRØNMO HOLDING AS

Org. no. 990824886 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 4.2m
Incorporated 2006
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).

GRØNMO HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 990824886. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Kjøp, eie og salg av aksjer og andre verdipapirer og tilhørende aktiviteter i forhold til dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 4.2m
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns GRØNMO HOLDING AS?

TERJE GRØNMO
GRØNMO HOLDING AS
NOK 0 rev. · NOK −23,000 profit

GRØNMO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRØNMO HOLDING AS own?

GRØNMO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRØNMO HOLDING AS

Who owns GRØNMO HOLDING AS?

TERJE GRØNMO is the largest registered owner, with 100.0%.

What is the revenue of GRØNMO HOLDING AS?

GRØNMO HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of GRØNMO HOLDING AS?

Terje Grønmo is registered as general manager of GRØNMO HOLDING AS.

Where is GRØNMO HOLDING AS based?

GRØNMO HOLDING 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.