BIZTRAC BETA
Manufacture of ready-mixed concrete

OH BETONG AS

Org. no. 923110860 Limited company (AS) Bergen Incorporated 1979 Active
Ownership graph ↗
Revenue 2024 NOK 54.4m
Operating profit NOK 3.1m
Equity NOK 16.6m
Incorporated 1979
Employees 14
Share capital NOK 400,000

OH BETONG AS is registered as a limited company in Bergen, Vestland with organisation number 923110860. The business is classified under manufacture of ready-mixed concrete (NACE 23.630). The company was incorporated in 1979 and has 14 registered employees. Registered share capital is NOK 400,000. The company's stated purpose is: “Industridrift og handel og hva dermed står i forbindelse, herunder ved innskudd av kapital, eventuelt ved aksjetegning å delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 54.4m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 54.4m
Operating profit
NOK 3.1m
Equity
NOK 16.6m
Est. value
NOK 20.4m

Financial health · 2024

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

Who owns OH BETONG AS?

ALT INVEST BERGEN AS
OH BETONG AS
NOK 54.4m rev. · NOK 3.1m profit

OH BETONG AS has 10 registered shareholders:

All shareholders and roles →

Which companies does OH BETONG AS own?

OH BETONG AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about OH BETONG AS

Who owns OH BETONG AS?

ALT INVEST BERGEN AS is the largest registered owner, with 36.0%.

What is the revenue of OH BETONG AS?

OH BETONG AS had revenue of NOK 54.4m in 2024.

Who is the general manager of OH BETONG AS?

Jan Otto Midttun is registered as general manager of OH BETONG AS.

Where is OH BETONG AS based?

OH BETONG AS has its business address in Indre Arna.

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.