BIZTRAC BETA
General medical practice activities

SAGA MEDISINSKE AS

Org. no. 932760657 Limited company (AS) Vestby Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −118,000
Equity NOK −285,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−285k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−118k kr).

SAGA MEDISINSKE AS is registered as a limited company in Vestby, Akershus with organisation number 932760657. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Legetjenester, bemanningsbyrå for helsetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −118,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −118,000
Equity
NOK −285,000

Financial health · 2025

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

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

Who owns SAGA MEDISINSKE AS?

SAGA MEDISINSKE HOLDING AS
SAGA MEDISINSKE AS
NOK 2.5m rev. · NOK −118,000 profit

SAGA MEDISINSKE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SAGA MEDISINSKE AS er morselskap for 1 datterselskap:

Frequently asked questions about SAGA MEDISINSKE AS

Who owns SAGA MEDISINSKE AS?

SAGA MEDISINSKE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SAGA MEDISINSKE AS?

SAGA MEDISINSKE AS had revenue of NOK 2.5m in 2025.

Where is SAGA MEDISINSKE AS based?

SAGA MEDISINSKE AS has its business address in Son.

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.