BIZTRAC BETA
Construction of residential and non-residential buildings

BN BYGGTEAM AS

Org. no. 913266609 Limited company (AS) Aurskog-Høland Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK 338,000
Equity NOK 2.5m
Incorporated 2014
Share capital NOK 30,000

BN BYGGTEAM AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 913266609. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygg og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK 338,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK 338,000
Equity
NOK 2.5m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns BN BYGGTEAM AS?

CHRISTIAN NILSSEN
BN BYGGTEAM AS
NOK 8.4m rev. · NOK 338,000 profit

BN BYGGTEAM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BN BYGGTEAM AS own?

BN BYGGTEAM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BN BYGGTEAM AS

Who owns BN BYGGTEAM AS?

CHRISTIAN NILSSEN is the largest registered owner, with 50.0%.

What is the revenue of BN BYGGTEAM AS?

BN BYGGTEAM AS had revenue of NOK 8.4m in 2024.

Who is the general manager of BN BYGGTEAM AS?

Christian Nilssen is registered as general manager of BN BYGGTEAM AS.

Where is BN BYGGTEAM AS based?

BN BYGGTEAM AS has its business address in Løken.

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.