BIZTRAC BETA
Business and other management consultancy activities

MIWELL NORGE AS

Org. no. 917193452 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 7,000
Equity NOK 77,000
Incorporated 2016
Share capital NOK 30,000

MIWELL NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 917193452. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Ledelse, analyse og andre konsulettjenester innen hotell, konferanse, restaurant og andre turismerelaterte bransjer og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 7,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 7,000
Equity
NOK 77,000
Est. value
NOK 74,000

Financial health · 2024

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

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

Who owns MIWELL NORGE AS?

MIWELL NORDIC AB
MIWELL NORGE AS
NOK 1.2m rev. · NOK 7,000 profit

MIWELL NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIWELL NORGE AS

Who owns MIWELL NORGE AS?

MIWELL NORDIC AB is the largest registered owner, with 100.0%.

What is the revenue of MIWELL NORGE AS?

MIWELL NORGE AS had revenue of NOK 1.2m in 2024.

Who is the general manager of MIWELL NORGE AS?

Thomas Hvalstad Ridder-Nielsen is registered as general manager of MIWELL NORGE AS.

Where is MIWELL NORGE AS based?

MIWELL NORGE 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.