BIZTRAC BETA
Mining of iron ores

KNABEN MOLYBDEN AS

Org. no. 989186833 Limited company (AS) Kvinesdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 34,000
Operating profit NOK −6,000
Equity NOK 551,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

KNABEN MOLYBDEN AS is registered as a limited company in Kvinesdal, Agder with organisation number 989186833. The business is classified under mining of iron ores (NACE 07.100). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bryting og produksjon av Molybden og andre mineraler, samt forretningsvirksomhet av enhver art, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 34,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 34,000
Operating profit
NOK −6,000
Equity
NOK 551,000
Est. value
NOK 294,000

Financial health · 2025

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

Who owns KNABEN MOLYBDEN AS?

SIGERSVOLD INVEST AS
KNABEN MOLYBDEN AS
NOK 34,000 rev. · NOK −6,000 profit

KNABEN MOLYBDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KNABEN MOLYBDEN AS

Who owns KNABEN MOLYBDEN AS?

SIGERSVOLD INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KNABEN MOLYBDEN AS?

KNABEN MOLYBDEN AS had revenue of NOK 34,000 in 2024.

Who is the general manager of KNABEN MOLYBDEN AS?

Andreas Sigersvold is registered as general manager of KNABEN MOLYBDEN AS.

Where is KNABEN MOLYBDEN AS based?

KNABEN MOLYBDEN AS has its business address in Kvinlog.

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.