BIZTRAC BETA
Construction of bridges and tunnels

TUNNELLBORING AS

Org. no. 934792416 Limited company (AS) Ullensvang Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK 121,000
Equity NOK 120,000
Incorporated 2024
Employees 10
Share capital NOK 30,000

Signals

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

TUNNELLBORING AS is registered as a limited company in Ullensvang, Vestland with organisation number 934792416. The business is classified under construction of bridges and tunnels (NACE 42.130). The company was incorporated in 2024 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tunnellboring og dertil knyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK 121,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK 121,000
Equity
NOK 120,000
Est. value
NOK 462,000

Financial health · 2025

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

Who owns TUNNELLBORING AS?

TE KVALVIK HOLDING AS
TUNNELLBORING AS
NOK 6.8m rev. · NOK 121,000 profit

TUNNELLBORING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TUNNELLBORING AS

Who owns TUNNELLBORING AS?

TE KVALVIK HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of TUNNELLBORING AS?

TUNNELLBORING AS had revenue of NOK 6.8m in 2025.

Who is the general manager of TUNNELLBORING AS?

Arne Dyngeland is registered as general manager of TUNNELLBORING AS.

Where is TUNNELLBORING AS based?

TUNNELLBORING AS has its business address in Utne.

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.