BIZTRAC BETA
Retail sale of medical and orthopaedic goods

LILLESTRØM OPTIKK AS

Org. no. 932376598 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 99,000
Equity NOK 366,000
Incorporated 2023
Share capital NOK 150,000

LILLESTRØM OPTIKK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932376598. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2023. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Detaljhandel innenfor den optiske bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 99,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 99,000
Equity
NOK 366,000
Est. value
NOK 563,000

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.3%
Good
Equity as a share of total capital

Who owns LILLESTRØM OPTIKK AS?

VIKAR OPTIKK AS
LILLESTRØM OPTIKK AS
NOK 2.8m rev. · NOK 99,000 profit

LILLESTRØM OPTIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LILLESTRØM OPTIKK AS own?

LILLESTRØM OPTIKK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LILLESTRØM OPTIKK AS

Who owns LILLESTRØM OPTIKK AS?

VIKAR OPTIKK AS is the largest registered owner, with 100.0%.

What is the revenue of LILLESTRØM OPTIKK AS?

LILLESTRØM OPTIKK AS had revenue of NOK 2.8m in 2025.

Who is the general manager of LILLESTRØM OPTIKK AS?

Øystein Aamodt is registered as general manager of LILLESTRØM OPTIKK AS.

Where is LILLESTRØM OPTIKK AS based?

LILLESTRØM OPTIKK AS has its business address in Lillestrøm.

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.