BIZTRAC BETA
Construction of residential and non-residential buildings

SVEIN BOGFJELLDAL AS

Org. no. 916772165 Limited company (AS) Vefsn Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 425,000
Operating profit NOK 6,000
Equity NOK 489,000
Incorporated 2016
Share capital NOK 30,000

SVEIN BOGFJELLDAL AS is registered as a limited company in Vefsn, Nordland with organisation number 916772165. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring av bygninger, tømrertjenester og det som naturlig faller sammen med dette. Samt investering i aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 425,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 425,000
Operating profit
NOK 6,000
Equity
NOK 489,000
Est. value
NOK 236,000

Financial health · 2025

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

Who owns SVEIN BOGFJELLDAL AS?

SVEIN OLE BOGFJELLDAL
SVEIN BOGFJELLDAL AS
NOK 425,000 rev. · NOK 6,000 profit

SVEIN BOGFJELLDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEIN BOGFJELLDAL AS

Who owns SVEIN BOGFJELLDAL AS?

SVEIN OLE BOGFJELLDAL is the largest registered owner, with 100.0%.

What is the revenue of SVEIN BOGFJELLDAL AS?

SVEIN BOGFJELLDAL AS had revenue of NOK 425,000 in 2025.

Who is the general manager of SVEIN BOGFJELLDAL AS?

Svein Ole Bogfjelldal is registered as general manager of SVEIN BOGFJELLDAL AS.

Where is SVEIN BOGFJELLDAL AS based?

SVEIN BOGFJELLDAL AS has its business address in Mosjøen.

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.