biztrac. BETA
COMPANY REGISTER PROFILE
933959066 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Operation of gravel and sand pits and mining of clay and kaolin

NORDSTEIN AS

Org. no. 933959066 Limited company (AS) Hareid Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 22,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

NORDSTEIN AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 933959066. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av massetak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 22,000
Est. value
NOK 21,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NORDSTEIN AS?

NORDSTEIN AS
NOK 0 rev. · NOK −8,000 profit

NORDSTEIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDSTEIN AS

Who owns NORDSTEIN AS?

Trond Åge Sørland is the largest registered owner, with 100.0%.

What is the revenue of NORDSTEIN AS?

NORDSTEIN AS had revenue of NOK 0 in 2025.

Who is the general manager of NORDSTEIN AS?

Knut Strømsjordet is registered as general manager of NORDSTEIN AS.

Where is NORDSTEIN AS based?

NORDSTEIN AS has its business address in Hareid.

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.