BIZTRAC BETA
Uoppgitt

NORSEWAY CONSULTING AS

Org. no. 931933981 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 14,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

NORSEWAY CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 931933981. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og investere i aksjer og andre verdipapirer, drive konsulentvirksomhet, samt tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 14,000
Est. value
NOK 16,000

Financial health · 2024

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

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

Who owns NORSEWAY CONSULTING AS?

SIGRUN SØRENSEN
NORSEWAY CONSULTING AS
NOK 0 rev. · NOK −7,000 profit

NORSEWAY CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORSEWAY CONSULTING AS own?

NORSEWAY CONSULTING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NORSEWAY CONSULTING AS

Who owns NORSEWAY CONSULTING AS?

SIGRUN SØRENSEN is the largest registered owner, with 100.0%.

What is the revenue of NORSEWAY CONSULTING AS?

NORSEWAY CONSULTING AS had revenue of NOK 0 in 2024.

Where is NORSEWAY CONSULTING AS based?

NORSEWAY CONSULTING 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.