biztrac. BETA
COMPANY REGISTER PROFILE
831278242 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Manufacture of other builders' carpentry and joinery

METKON AS

Org. no. 831278242 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 81,000
Equity NOK 128,000
Incorporated 2023
Share capital NOK 30,000

METKON AS is registered as a limited company in Oslo, Oslo with organisation number 831278242. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon og installasjon av trapper og rekkverk og annet som faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 81,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
▲ +837 %
Operating profit
NOK 81,000
▲ +1520 %
Equity
NOK 128,000
▲ +83 %
Est. value
NOK 329,000

Financial health · 2025

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
15.9%
Very good
Return on total assets
Solidity
14.6%
Satisfactory
Equity as a share of total capital

Who owns METKON AS?

METKON ALUMIINIMUM OÜ EE
METKON PROJEKT OÜ EE
METKON AS
NOK 2.2m rev. · NOK 81,000 profit

METKON AS has 2 registered shareholders:

  • METKON ALUMIINIMUM OÜ 50.0%
  • METKON PROJEKT OÜ 50.0%
All shareholders and roles →

Frequently asked questions about METKON AS

Who owns METKON AS?

METKON ALUMIINIMUM OÜ is the largest registered owner, with 50.0%.

What is the revenue of METKON AS?

METKON AS had revenue of NOK 2.2m in 2025.

Who is the general manager of METKON AS?

Mihkel Leps is registered as general manager of METKON AS.

Where is METKON AS based?

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