BIZTRAC BETA
Business and other management consultancy activities

GRØNNERØE AS

Org. no. 980745376 Limited company (AS) Trondheim Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −242,000
Equity NOK 19.2m
Incorporated 1999
Share capital NOK 100,000

Signals

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

GRØNNERØE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 980745376. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Finansiell virksomhet og rådgivningstjenester”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −242,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −242,000
Equity
NOK 19.2m
Est. value
NOK 43.7m

Financial health · 2025

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

Who owns GRØNNERØE AS?

STEIN RAGNAR GRØNNERØE
GRØNNERØE AS
NOK 0 rev. · NOK −242,000 profit

GRØNNERØE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRØNNERØE AS own?

GRØNNERØE AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about GRØNNERØE AS

Who owns GRØNNERØE AS?

STEIN RAGNAR GRØNNERØE is the largest registered owner, with 100.0%.

What is the revenue of GRØNNERØE AS?

GRØNNERØE AS had revenue of NOK 0 in 2025.

Who is the general manager of GRØNNERØE AS?

Stein Ragnar Grønnerøe is registered as general manager of GRØNNERØE AS.

Where is GRØNNERØE AS based?

GRØNNERØE AS has its business address in Trondheim.

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.