BIZTRAC BETA
Dental practice care activities

OSS-TO INVEST AS

Org. no. 931717472 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 2.4m
Equity NOK 13.2m
Incorporated 2023
Share capital NOK 100,000

OSS-TO INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931717472. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, forvalte og investere i aksjer og andeler i andre selskaper, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 2.4m
Equity
NOK 13.2m
Est. value
NOK 18.6m

Financial health · 2025

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

Who owns OSS-TO INVEST AS?

OLAV INGE LARSEN
OSS-TO INVEST AS
NOK 2.5m rev. · NOK 2.4m profit

OSS-TO INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OSS-TO INVEST AS own?

OSS-TO INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OSS-TO INVEST AS

Who owns OSS-TO INVEST AS?

OLAV INGE LARSEN is the largest registered owner, with 50.0%.

What is the revenue of OSS-TO INVEST AS?

OSS-TO INVEST AS had revenue of NOK 2.5m in 2025.

Who is the general manager of OSS-TO INVEST AS?

Therese Husby Larsen is registered as general manager of OSS-TO INVEST AS.

Where is OSS-TO INVEST AS based?

OSS-TO INVEST AS has its business address in Trondheim.

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.