BIZTRAC BETA
Rental and operating of own or leased real estate

TYNSETBYGG EIENDOM AS

Org. no. 922721378 Limited company (AS) Tynset Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 616,000
Operating profit NOK 439,000
Equity NOK 824,000
Incorporated 2019
Share capital NOK 79,000

TYNSETBYGG EIENDOM AS is registered as a limited company in Tynset, Innlandet with organisation number 922721378. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 79,000, divided into 500 shares. The company's stated purpose is: “Eie og utleie av fast eiendom og dermed beslektet virksomhet, samt ved aksjetegning eller på annen måte forestå eller delta i virksomhet av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 616,000 in revenue and NOK 439,000 in operating profit.

Key figures · 2025

Revenue
NOK 616,000
Operating profit
NOK 439,000
Equity
NOK 824,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns TYNSETBYGG EIENDOM AS?

JOHN HARALD ØVERLI
TYNSETBYGG EIENDOM AS
NOK 616,000 rev. · NOK 439,000 profit

TYNSETBYGG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TYNSETBYGG EIENDOM AS

Who owns TYNSETBYGG EIENDOM AS?

JOHN HARALD ØVERLI is the largest registered owner, with 50.0%.

What is the revenue of TYNSETBYGG EIENDOM AS?

TYNSETBYGG EIENDOM AS had revenue of NOK 616,000 in 2025.

Who is the general manager of TYNSETBYGG EIENDOM AS?

Magne Egil Westum is registered as general manager of TYNSETBYGG EIENDOM AS.

Where is TYNSETBYGG EIENDOM AS based?

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