BIZTRAC BETA
Construction of residential and non-residential buildings

TYRI BYGG AS

Org. no. 933987132 Limited company (AS) Holmestrand Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 8.1m
Operating profit NOK 37,000
Equity NOK 1.4m
Incorporated 2024
Employees 7
Share capital NOK 140,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TYRI BYGG AS is registered as a limited company in Holmestrand, Vestfold with organisation number 933987132. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024 and has 7 registered employees. Registered share capital is NOK 140,000, divided into 3000 shares. The company's stated purpose is: “Oppføring av bygg og anlegg samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.1m in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.1m
Operating profit
NOK 37,000
Equity
NOK 1.4m
Est. value
NOK 699,000

Financial health · 2025

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

Who owns TYRI BYGG AS?

ØNNEMØRK AS
TYRI BYGG AS
NOK 8.1m rev. · NOK 37,000 profit

TYRI BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TYRI BYGG AS

Who owns TYRI BYGG AS?

ØNNEMØRK AS is the largest registered owner, with 100.0%.

What is the revenue of TYRI BYGG AS?

TYRI BYGG AS had revenue of NOK 8.1m in 2025.

Who is the general manager of TYRI BYGG AS?

Stig Guttormsen is registered as general manager of TYRI BYGG AS.

Where is TYRI BYGG AS based?

TYRI BYGG AS has its business address in Hof.

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.