BIZTRAC BETA
Construction of roads and motorways

T.H VALBY ASFALT & GRAVING AS

Org. no. 918644962 Limited company (AS) Ullensaker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 895,000
Equity NOK 993,000
Incorporated 2017
Share capital NOK 30,000

T.H VALBY ASFALT & GRAVING AS is registered as a limited company in Ullensaker, Akershus with organisation number 918644962. The business is classified under construction of roads and motorways (NACE 42.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Entreprenørvirksomhet herunder asfaltering og gravearbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 895,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 895,000
Equity
NOK 993,000
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns T.H VALBY ASFALT & GRAVING AS?

THOR HARALD VALBY
T.H VALBY ASFALT & GRAVING AS
NOK 3.5m rev. · NOK 895,000 profit

T.H VALBY ASFALT & GRAVING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about T.H VALBY ASFALT & GRAVING AS

Who owns T.H VALBY ASFALT & GRAVING AS?

THOR HARALD VALBY is the largest registered owner, with 100.0%.

What is the revenue of T.H VALBY ASFALT & GRAVING AS?

T.H VALBY ASFALT & GRAVING AS had revenue of NOK 3.5m in 2025.

Who is the general manager of T.H VALBY ASFALT & GRAVING AS?

Thor Harald Valby is registered as general manager of T.H VALBY ASFALT & GRAVING AS.

Where is T.H VALBY ASFALT & GRAVING AS based?

T.H VALBY ASFALT & GRAVING AS has its business address in Jessheim.

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.