BIZTRAC BETA
Construction of residential and non-residential buildings

ØRLAND BYGGTJENESTER AS

Org. no. 930878383 Limited company (AS) Orkland Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 319,000
Equity NOK 146,000
Incorporated 2023
Share capital NOK 60,000

ØRLAND BYGGTJENESTER AS is registered as a limited company in Orkland, Trøndelag with organisation number 930878383. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Utføre tjenester i forbindelse med oppføring av byggverk. Betong og tømrerarbeid samt byggeledelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 319,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 319,000
Equity
NOK 146,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.8%
Satisfactory
Equity as a share of total capital

Who owns ØRLAND BYGGTJENESTER AS?

TORGEIR TANGVIK
ØRLAND BYGGTJENESTER AS
NOK 4.3m rev. · NOK 319,000 profit

ØRLAND BYGGTJENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØRLAND BYGGTJENESTER AS

Who owns ØRLAND BYGGTJENESTER AS?

TORGEIR TANGVIK is the largest registered owner, with 50.0%.

What is the revenue of ØRLAND BYGGTJENESTER AS?

ØRLAND BYGGTJENESTER AS had revenue of NOK 4.3m in 2025.

Who is the general manager of ØRLAND BYGGTJENESTER AS?

Torgeir Tangvik is registered as general manager of ØRLAND BYGGTJENESTER AS.

Where is ØRLAND BYGGTJENESTER AS based?

ØRLAND BYGGTJENESTER AS has its business address in Orkanger.

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.