BIZTRAC BETA
Rental and operating of own or leased real estate

METKO AS

Org. no. 976577019 Limited company (AS) Trondheim Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −177,000
Equity NOK 9.6m
Incorporated 1996
Share capital NOK 236,000

Signals

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

METKO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 976577019. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 236,000, divided into 236 shares. The company's stated purpose is: “Finans- og investeringsvirksomhet, herunder kjøp, salg og forvaltning av fast eiendom, kjøp og salg av verdipapirer og kjøp og salg av bildende kunst, samt å delta i andre selskaper og innretninger innenfor samme områder. ”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −177,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −177,000
Equity
NOK 9.6m
Est. value
NOK 11.0m

Financial health · 2024

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

Who owns METKO AS?

GUDMUND KORAN
METKO AS
NOK 0 rev. · NOK −177,000 profit

METKO AS has 5 registered shareholders:

All shareholders and roles →

Which companies does METKO AS own?

METKO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about METKO AS

Who owns METKO AS?

GUDMUND KORAN is the largest registered owner, with 41.1%.

What is the revenue of METKO AS?

METKO AS had revenue of NOK 0 in 2024.

Where is METKO AS based?

METKO 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.