BIZTRAC BETA
Rental and operating of own or leased real estate

TYNSET OPTISKE EIENDOM AS

Org. no. 830498222 Limited company (AS) Tynset Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 300,000
Operating profit NOK 221,000
Equity NOK 745,000
Incorporated 2022
Share capital NOK 46,000

TYNSET OPTISKE EIENDOM AS is registered as a limited company in Tynset, Innlandet with organisation number 830498222. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 46,000, divided into 45600 shares. The company's stated purpose is: “Kjøp/drift av fast eiendom og tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 300,000 in revenue and NOK 221,000 in operating profit.

Key figures · 2025

Revenue
NOK 300,000
Operating profit
NOK 221,000
Equity
NOK 745,000
Est. value
NOK 995,000

Financial health · 2025

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

Who owns TYNSET OPTISKE EIENDOM AS?

BRYNHILD NYGARD
TYNSET OPTISKE EIENDOM AS
NOK 300,000 rev. · NOK 221,000 profit

TYNSET OPTISKE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TYNSET OPTISKE EIENDOM AS

Who owns TYNSET OPTISKE EIENDOM AS?

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

What is the revenue of TYNSET OPTISKE EIENDOM AS?

TYNSET OPTISKE EIENDOM AS had revenue of NOK 300,000 in 2025.

Where is TYNSET OPTISKE EIENDOM AS based?

TYNSET OPTISKE EIENDOM 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.