BIZTRAC BETA
Construction of residential and non-residential buildings

FLEKKEFJORD BYGG AS

Org. no. 914916224 Limited company (AS) Flekkefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 139,000
Equity NOK 330,000
Incorporated 2015
Share capital NOK 30,000

FLEKKEFJORD BYGG AS is registered as a limited company in Flekkefjord, Agder with organisation number 914916224. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Snekkerarbeid, reparasjon og vedlikehold av bygninger, oppføring av nybygg, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 139,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 139,000
Equity
NOK 330,000
Est. value
NOK 572,000

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.7%
Good
Equity as a share of total capital

Who owns FLEKKEFJORD BYGG AS?

SVEIN MARTIN HELLESTØL
FLEKKEFJORD BYGG AS
NOK 6.6m rev. · NOK 139,000 profit

FLEKKEFJORD BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLEKKEFJORD BYGG AS

Who owns FLEKKEFJORD BYGG AS?

SVEIN MARTIN HELLESTØL is the largest registered owner, with 50.0%.

What is the revenue of FLEKKEFJORD BYGG AS?

FLEKKEFJORD BYGG AS had revenue of NOK 6.6m in 2024.

Who is the general manager of FLEKKEFJORD BYGG AS?

Svein Martin Hellestøl is registered as general manager of FLEKKEFJORD BYGG AS.

Where is FLEKKEFJORD BYGG AS based?

FLEKKEFJORD BYGG AS has its business address in Flekkefjord.

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.