BIZTRAC BETA
Other specialised construction activities n.e.c.

FA BETONG AS

Org. no. 921862806 Limited company (AS) Lyngdal Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 49.3m
Operating profit NOK 2.3m
Equity NOK 8.9m
Incorporated 2018
Employees 12
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FA BETONG AS is registered as a limited company in Lyngdal, Agder with organisation number 921862806. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2018 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Betongarbeid og deltakelse i andre selskaper samt annet som står i naturlig forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 49.3m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 49.3m
Operating profit
NOK 2.3m
Equity
NOK 8.9m
Est. value
NOK 12.6m

Financial health · 2025

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

Who owns FA BETONG AS?

FRODE A. HOLDING AS
FA BETONG AS
NOK 49.3m rev. · NOK 2.3m profit

FA BETONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FA BETONG AS

Who owns FA BETONG AS?

FRODE A. HOLDING AS is the largest registered owner, with 55.0%.

What is the revenue of FA BETONG AS?

FA BETONG AS had revenue of NOK 49.3m in 2025.

Who is the general manager of FA BETONG AS?

Frode Andersen is registered as general manager of FA BETONG AS.

Where is FA BETONG AS based?

FA BETONG AS has its business address in Lyngdal.

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.