BIZTRAC BETA
Site preparation

ULF REIDAR TØNNESSEN AS

Org. no. 925583170 Limited company (AS) Lillesand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 810,000
Equity NOK 1.9m
Incorporated 2020
Share capital NOK 30,000

ULF REIDAR TØNNESSEN AS is registered as a limited company in Lillesand, Agder with organisation number 925583170. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Grunnarbeid, og spesialisert bygge- og anleggsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 810,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 810,000
Equity
NOK 1.9m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns ULF REIDAR TØNNESSEN AS?

ULF REIDAR TØNNESSEN
ULF REIDAR TØNNESSEN AS
NOK 3.0m rev. · NOK 810,000 profit

ULF REIDAR TØNNESSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ULF REIDAR TØNNESSEN AS own?

ULF REIDAR TØNNESSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ULF REIDAR TØNNESSEN AS

Who owns ULF REIDAR TØNNESSEN AS?

ULF REIDAR TØNNESSEN is the largest registered owner, with 100.0%.

What is the revenue of ULF REIDAR TØNNESSEN AS?

ULF REIDAR TØNNESSEN AS had revenue of NOK 3.0m in 2025.

Who is the general manager of ULF REIDAR TØNNESSEN AS?

Ulf Reidar Tønnessen is registered as general manager of ULF REIDAR TØNNESSEN AS.

Where is ULF REIDAR TØNNESSEN AS based?

ULF REIDAR TØNNESSEN AS has its business address in Lillesand.

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.