BIZTRAC BETA
Other specialised construction activities in construction of buildings

BUFLATEN BETONGSERVICE AS

Org. no. 830607552 Limited company (AS) Froland Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 16,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

BUFLATEN BETONGSERVICE AS is registered as a limited company in Froland, Agder with organisation number 830607552. 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 100 shares. The company's stated purpose is: “Betong og tømrerarbeid og annet spesialisert bygge- og anleggsarbeid, produksjon og salg, samt hva som naturlig faller sammen med dette. Selskapet kan eie aksjer/andeler i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK 16,000
Est. value
NOK 17,000

Financial health · 2024

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.0%
Weak
Equity as a share of total capital

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

Who owns BUFLATEN BETONGSERVICE AS?

INGAR JOMÅS BUFLATEN
BUFLATEN BETONGSERVICE AS
· NOK −5,000 profit

BUFLATEN BETONGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BUFLATEN BETONGSERVICE AS own?

BUFLATEN BETONGSERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BUFLATEN BETONGSERVICE AS

Who owns BUFLATEN BETONGSERVICE AS?

INGAR JOMÅS BUFLATEN is the largest registered owner, with 100.0%.

Where is BUFLATEN BETONGSERVICE AS based?

BUFLATEN BETONGSERVICE AS has its business address in Froland.

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.