BIZTRAC BETA
COMPANY REGISTER PROFILE
987835729 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Joinery installation

TYRHAUG AS

Org. no. 987835729 Limited company (AS) Ørland Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 203,000
Equity NOK 3.1m
Incorporated 2005
Share capital NOK 200,000

TYRHAUG AS is registered as a limited company in Ørland, Trøndelag with organisation number 987835729. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Bygg og anlegg. Snekkering og andre produkter/tjenester som naturlig hører sammen med 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 1.1m in revenue and NOK 203,000 in operating profit.

Former names: IDÈBYGG AS

Key figures · 2025

Revenue
NOK 1.1m
▲ +53 %
Operating profit
NOK 203,000
▲ +244 %
Equity
NOK 3.1m
▲ +6 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
5.84
Very good
Current assets ÷ current liabilities
Profitability
5.8%
Weak
Return on total assets
Solidity
94.7%
Very good
Equity as a share of total capital

Who owns TYRHAUG AS?

TYRHAUG AS
NOK 1.1m rev. · NOK 203,000 profit

TYRHAUG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TYRHAUG AS

Who owns TYRHAUG AS?

CECILIE TYRHAUG is the largest registered owner, with 50.0%.

What is the revenue of TYRHAUG AS?

TYRHAUG AS had revenue of NOK 1.1m in 2025.

Who is the general manager of TYRHAUG AS?

Cecilie Tyrhaug is registered as general manager of TYRHAUG AS.

Where is TYRHAUG AS based?

TYRHAUG AS has its business address in Bjugn.

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

Report a problem

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