BIZTRAC BETA
Other health services

LINSOTEKET AS

Org. no. 926788299 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 502,000
Equity NOK −411,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−411k kr).
  • Nylig endring 2026-07-07 Adresseendring registrert 2026-07-07.

LINSOTEKET AS is registered as a limited company in Oslo, Oslo with organisation number 926788299. The business is classified under other health services (NACE 86.993). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kliniske tjenester innen optikervirksomhet, samt salg av kontaktlinser og pleieprodukter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 502,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 502,000
Equity
NOK −411,000
Est. value
NOK 2.8m

Financial health · 2024

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

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

Who owns LINSOTEKET AS?

GUSTAV BENGT LEON STENSSON
LINSOTEKET AS
NOK 1.4m rev. · NOK 502,000 profit

LINSOTEKET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LINSOTEKET AS own?

LINSOTEKET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LINSOTEKET AS

Who owns LINSOTEKET AS?

GUSTAV BENGT LEON STENSSON is the largest registered owner, with 100.0%.

What is the revenue of LINSOTEKET AS?

LINSOTEKET AS had revenue of NOK 1.4m in 2024.

Where is LINSOTEKET AS based?

LINSOTEKET 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.