biztrac. BETA
COMPANY REGISTER PROFILE
927484889 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

B4 BYGG AS

Org. no. 927484889 Limited company (AS) Fauske Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 12.5m
Operating profit NOK 734,000
Equity NOK 2.5m
Incorporated 2021
Employees 10
Share capital NOK 600,000

B4 BYGG AS is registered as a limited company in Fauske, Nordland with organisation number 927484889. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 10 registered employees. Registered share capital is NOK 600,000, divided into 60000 shares. The company's stated purpose is: “Entreprenør virksomhet innen bygg og anlegg, kjøp og salg av eiendom, varer og tjenester og det som hører til bygg og anleggsbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.5m in revenue and NOK 734,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.5m
▲ +59 %
Operating profit
NOK 734,000
▲ +56 %
Equity
NOK 2.5m
▲ +22 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
2.31
Very good
Current assets ÷ current liabilities
Profitability
12.8%
Good
Return on total assets
Solidity
42.1%
Very good
Equity as a share of total capital

Who owns B4 BYGG AS?

B4 BYGG AS
NOK 12.5m rev. · NOK 734,000 profit

B4 BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about B4 BYGG AS

Who owns B4 BYGG AS?

B4 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of B4 BYGG AS?

B4 BYGG AS had revenue of NOK 12.5m in 2025.

Who is the general manager of B4 BYGG AS?

Magnus Blekastad is registered as general manager of B4 BYGG AS.

Where is B4 BYGG AS based?

B4 BYGG AS has its business address in Fauske.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.