BIZTRAC BETA
General medical practice activities

DR. MOE AS

Org. no. 926491431 Limited company (AS) Melhus Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 861,000
Equity NOK 4.4m
Incorporated 2021
Share capital NOK 30,000

DR. MOE AS is registered as a limited company in Melhus, Trøndelag with organisation number 926491431. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Legesenter, undervisning og rådgivende virksomhet, salg og utvikling av IT-produkter, investering i fast eiendom og aksjer, samt deltakelse i liknende selskap, samt alt hva som dertil faller under.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 861,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 861,000
Equity
NOK 4.4m
Est. value
NOK 6.5m

Financial health · 2025

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

Who owns DR. MOE AS?

KRISTOFFER ØLSTØREN-MOE
DR. MOE AS
NOK 3.8m rev. · NOK 861,000 profit

DR. MOE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DR. MOE AS own?

DR. MOE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about DR. MOE AS

Who owns DR. MOE AS?

KRISTOFFER ØLSTØREN-MOE is the largest registered owner, with 100.0%.

What is the revenue of DR. MOE AS?

DR. MOE AS had revenue of NOK 3.8m in 2025.

Who is the general manager of DR. MOE AS?

Kristoffer Ølstøren-Moe is registered as general manager of DR. MOE AS.

Where is DR. MOE AS based?

DR. MOE AS has its business address in Melhus.

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.