BIZTRAC BETA
Retail sale of medical and orthopaedic goods

TYNSET OPTISKE AS

Org. no. 979270275 Limited company (AS) Tynset Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 8.9m
Operating profit NOK 2.0m
Equity NOK 3.7m
Incorporated 1997
Employees 6
Share capital NOK 74,000

TYNSET OPTISKE AS is registered as a limited company in Tynset, Innlandet with organisation number 979270275. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 1997 and has 6 registered employees. Registered share capital is NOK 74,000, divided into 74400 shares. The company's stated purpose is: “Optiske tjenester og service, samt selge varer innen bransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.9m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 8.9m
Operating profit
NOK 2.0m
Equity
NOK 3.7m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns TYNSET OPTISKE AS?

BRYNHILD NYGARD
TYNSET OPTISKE AS
NOK 8.9m rev. · NOK 2.0m profit

TYNSET OPTISKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TYNSET OPTISKE AS own?

TYNSET OPTISKE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TYNSET OPTISKE AS

Who owns TYNSET OPTISKE AS?

BRYNHILD NYGARD is the largest registered owner, with 100.0%.

What is the revenue of TYNSET OPTISKE AS?

TYNSET OPTISKE AS had revenue of NOK 8.9m in 2024.

Who is the general manager of TYNSET OPTISKE AS?

Trude Nygard Johansen is registered as general manager of TYNSET OPTISKE AS.

Where is TYNSET OPTISKE AS based?

TYNSET OPTISKE AS has its business address in Tynset.

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.