BIZTRAC BETA
Joinery installation

MIDTUN BETONG AS

Org. no. 832197602 Limited company (AS) Ullensvang Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 361,000
Operating profit NOK 77,000
Equity NOK 90,000
Incorporated 2023
Share capital NOK 30,000

MIDTUN BETONG AS is registered as a limited company in Ullensvang, Vestland with organisation number 832197602. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen snekkerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 361,000 in revenue and NOK 77,000 in operating profit.

Key figures · 2025

Revenue
NOK 361,000
Operating profit
NOK 77,000
Equity
NOK 90,000
Est. value
NOK 272,000

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MIDTUN BETONG AS?

PER-CHRISTIAN MIDTUN
MIDTUN BETONG AS
NOK 361,000 rev. · NOK 77,000 profit

MIDTUN BETONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MIDTUN BETONG AS

Who owns MIDTUN BETONG AS?

PER-CHRISTIAN MIDTUN is the largest registered owner, with 50.0%.

What is the revenue of MIDTUN BETONG AS?

MIDTUN BETONG AS had revenue of NOK 361,000 in 2025.

Who is the general manager of MIDTUN BETONG AS?

Per-Christian Midtun is registered as general manager of MIDTUN BETONG AS.

Where is MIDTUN BETONG AS based?

MIDTUN BETONG AS has its business address in Jondal.

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.