BIZTRAC BETA
Other specialised construction activities in construction of buildings

SÆLA BETONG AS

Org. no. 928931544 Limited company (AS) Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 811,000
Operating profit NOK 163,000
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

SÆLA BETONG AS is registered as a limited company in Hå, Rogaland with organisation number 928931544. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Levere prosjekt-, håndverks- og entreprenørtjenester samt delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 811,000 in revenue and NOK 163,000 in operating profit.

Key figures · 2025

Revenue
NOK 811,000
Operating profit
NOK 163,000
Equity
NOK 30,000
Est. value
NOK 432,000

Financial health · 2025

Liquidity
2.09
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.0%
Weak
Equity as a share of total capital

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

Who owns SÆLA BETONG AS?

KRISTOFFER SÆLA TAKSDAL
SÆLA BETONG AS
NOK 811,000 rev. · NOK 163,000 profit

SÆLA BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SÆLA BETONG AS

Who owns SÆLA BETONG AS?

KRISTOFFER SÆLA TAKSDAL is the largest registered owner, with 100.0%.

What is the revenue of SÆLA BETONG AS?

SÆLA BETONG AS had revenue of NOK 811,000 in 2025.

Who is the general manager of SÆLA BETONG AS?

Kristoffer Sæla Taksdal is registered as general manager of SÆLA BETONG AS.

Where is SÆLA BETONG AS based?

SÆLA BETONG AS has its business address in Nærbø.

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.