BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

OSLO SPINE AS

Org. no. 924925728 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK −13,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−13k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

OSLO SPINE AS is registered as a limited company in Oslo, Oslo with organisation number 924925728. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Medisinsk behandling og rådgiving relatert til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK −13,000

Financial health · 2025

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

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

Who owns OSLO SPINE AS?

MAJORSTUEN SPESIALISTSENTER AS
OSLO SPINE AS
NOK 0 rev. · NOK −5,000 profit

OSLO SPINE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO SPINE AS

Who owns OSLO SPINE AS?

MAJORSTUEN SPESIALISTSENTER AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO SPINE AS?

OSLO SPINE AS had revenue of NOK 0 in 2024.

Who is the general manager of OSLO SPINE AS?

Jo Andreas Ording is registered as general manager of OSLO SPINE AS.

Where is OSLO SPINE AS based?

OSLO SPINE 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.