BIZTRAC BETA
Rental and operating of own or leased real estate

GRØNN OVERLEDNING AS

Org. no. 918512330 Limited company (AS) Nærøysund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −21,000
Equity NOK 659,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

GRØNN OVERLEDNING AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 918512330. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i andre selskap, og det som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK 659,000
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns GRØNN OVERLEDNING AS?

HÅVAR MARTIN BREDESEN
GRØNN OVERLEDNING AS
NOK 0 rev. · NOK −21,000 profit

GRØNN OVERLEDNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRØNN OVERLEDNING AS own?

GRØNN OVERLEDNING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRØNN OVERLEDNING AS

Who owns GRØNN OVERLEDNING AS?

HÅVAR MARTIN BREDESEN is the largest registered owner, with 100.0%.

What is the revenue of GRØNN OVERLEDNING AS?

GRØNN OVERLEDNING AS had revenue of NOK 0 in 2024.

Where is GRØNN OVERLEDNING AS based?

GRØNN OVERLEDNING AS has its business address in Ottersøy.

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.