BIZTRAC BETA
Construction of residential and non-residential buildings

SVELGEN BYGG AS

Org. no. 914166381 Limited company (AS) Bremanger Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 16.4m
Operating profit NOK 802,000
Equity NOK 705,000
Incorporated 2014
Employees 16
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.

SVELGEN BYGG AS is registered as a limited company in Bremanger, Vestland with organisation number 914166381. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet og oppføring, kjøp og salg av fast eiendom, salg og leveranser av bygningsmateriell og virksomhet som er relatert til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.4m in revenue and NOK 802,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.4m
Operating profit
NOK 802,000
Equity
NOK 705,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns SVELGEN BYGG AS?

BU OG FRITID AS
SVELGEN BYGG AS
NOK 16.4m rev. · NOK 802,000 profit

SVELGEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVELGEN BYGG AS

Who owns SVELGEN BYGG AS?

BU OG FRITID AS is the largest registered owner, with 100.0%.

What is the revenue of SVELGEN BYGG AS?

SVELGEN BYGG AS had revenue of NOK 16.4m in 2024.

Where is SVELGEN BYGG AS based?

SVELGEN BYGG AS has its business address in Svelgen.

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.