BIZTRAC BETA
Other mining and quarrying n.e.c.

NORKALSITT AS

Org. no. 957031110 Limited company (AS) Oslo Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 548,000
Operating profit NOK 44,000
Equity NOK 4.5m
Incorporated 1990
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORKALSITT AS is registered as a limited company in Oslo, Oslo with organisation number 957031110. The business is classified under other mining and quarrying n.e.c. (NACE 08.990). The company was incorporated in 1990. Registered share capital is NOK 500,000, divided into 50000 shares. The company's stated purpose is: “Utvinning og produksjon av mineral produkter samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 548,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2024

Revenue
NOK 548,000
Operating profit
NOK 44,000
Equity
NOK 4.5m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns NORKALSITT AS?

SCANDIUM AS
NORKALSITT AS
NOK 548,000 rev. · NOK 44,000 profit

NORKALSITT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORKALSITT AS

Who owns NORKALSITT AS?

SCANDIUM AS is the largest registered owner, with 100.0%.

What is the revenue of NORKALSITT AS?

NORKALSITT AS had revenue of NOK 548,000 in 2024.

Who is the general manager of NORKALSITT AS?

Mette Svanhild Hoff Sverdvik is registered as general manager of NORKALSITT AS.

Where is NORKALSITT AS based?

NORKALSITT 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 15.06.2026.

Report a problem

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