BIZTRAC BETA
Specialised construction activities in civil engineering

OMMEDAL & SØNNER AS

Org. no. 934033302 Limited company (AS) Tønsberg Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 43.4m
Operating profit NOK 856,000
Equity NOK 10.6m
Incorporated 1983
Employees 18
Share capital NOK 100,000

OMMEDAL & SØNNER AS is registered as a limited company in Tønsberg, Vestfold with organisation number 934033302. The business is classified under specialised construction activities in civil engineering (NACE 43.500). The company was incorporated in 1983 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Entreprenørvirksomhet og annen virksomhet som har tilknytning til dette og eventuelt å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 43.4m in revenue and NOK 856,000 in operating profit.

Key figures · 2024

Revenue
NOK 43.4m
Operating profit
NOK 856,000
Equity
NOK 10.6m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns OMMEDAL & SØNNER AS?

OMMEDAL EIENDOM AS
OMMEDAL & SØNNER AS
NOK 43.4m rev. · NOK 856,000 profit

OMMEDAL & SØNNER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about OMMEDAL & SØNNER AS

Who owns OMMEDAL & SØNNER AS?

OMMEDAL EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of OMMEDAL & SØNNER AS?

OMMEDAL & SØNNER AS had revenue of NOK 43.4m in 2024.

Who is the general manager of OMMEDAL & SØNNER AS?

Runar Ommedal is registered as general manager of OMMEDAL & SØNNER AS.

Where is OMMEDAL & SØNNER AS based?

OMMEDAL & SØNNER AS has its business address in Våle.

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.