biztrac. BETA
COMPANY REGISTER PROFILE
985090181 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Casting of other non-ferrous metals

METALLCO NORGE AS

Org. no. 985090181 Limited company (AS) Oslo Incorporated 2002 Active
Operating profit NOK −31,000
Equity NOK 518,000
Incorporated 2002
Share capital NOK 500,000

Signals

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

METALLCO NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 985090181. The business is classified under casting of other non-ferrous metals (NACE 24.540). The company was incorporated in 2002. Registered share capital is NOK 500,000, divided into 8000 shares. The company's stated purpose is: “Utføring av byggeprosjekter, investering i fast eiendom, herunder utleie, drift, kjøp og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tillegg kommer annen nærliggende virksomhet.”.

Former names: RAUFOSS METALL AS

Key figures · 2025

Operating profit
NOK −31,000
▼ −1 %
Equity
NOK 518,000
▲ +0 %
Est. value
NOK 608,000

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 METALLCO NORGE AS?

METALLCO NORGE AS
· NOK −31,000 profit

METALLCO NORGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

METALLCO NORGE AS er morselskap for 32 datterselskaper:

Frequently asked questions about METALLCO NORGE AS

Who owns METALLCO NORGE AS?

METALLCO OPPLAND AS is the largest registered owner, with 100.0%.

Who is the general manager of METALLCO NORGE AS?

Tord Linnerud is registered as general manager of METALLCO NORGE AS.

Where is METALLCO NORGE AS based?

METALLCO NORGE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.