biztrac. BETA
COMPANY REGISTER PROFILE
932612755 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER

Org. no. 932612755 Condominium flat owner (ESEK) Vang Incorporated 2023 Active
Revenue 2025 NOK 403,000
Operating profit NOK 41,000
Equity NOK 173,000
Incorporated 2023

SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER is registered as a condominium flat owner in Vang, Innlandet with organisation number 932612755. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2023. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 403,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 403,000
▲ +19 %
Operating profit
NOK 41,000
▼ −69 %
Equity
NOK 173,000
▲ +32 %
Est. value
NOK 322,000

Financial health · 2025

Liquidity
10.29
Very good
Current assets ÷ current liabilities
Profitability
16.2%
Very good
Return on total assets
Solidity
67.0%
Very good
Equity as a share of total capital

Who owns SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER?

No shareholders are registered for SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER

What is the revenue of SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER?

SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER had revenue of NOK 403,000 in 2025.

Where is SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER based?

SAMEIET TYIN - JOTUNHEIMEN HØYFJELLSHYTTER OG LEILIGHETER has its business address in Tyinkrysset.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.