biztrac. BETA
COMPANY REGISTER PROFILE
920794882 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

B.I.S. BYGG AS

Org. no. 920794882 Limited company (AS) Alta Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 562,000
Equity NOK 639,000
Incorporated 2018
Share capital NOK 30,000

B.I.S. BYGG AS is registered as a limited company in Alta, Finnmark with organisation number 920794882. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømring, bygningsmessige arbeider, garasje, nybygg, tilbygg, hytte, rehabilitering og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 562,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
▲ +4 %
Operating profit
NOK 562,000
▲ +80 %
Equity
NOK 639,000
▲ +44 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
13.7%
Good
Return on total assets
Solidity
12.9%
Satisfactory
Equity as a share of total capital

Who owns B.I.S. BYGG AS?

B.I.S. BYGG AS
NOK 7.0m rev. · NOK 562,000 profit

B.I.S. BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about B.I.S. BYGG AS

Who owns B.I.S. BYGG AS?

Bernt Ivar Strøm is the largest registered owner, with 100.0%.

What is the revenue of B.I.S. BYGG AS?

B.I.S. BYGG AS had revenue of NOK 7.0m in 2025.

Who is the general manager of B.I.S. BYGG AS?

Bernt Ivar Strøm is registered as general manager of B.I.S. BYGG AS.

Where is B.I.S. BYGG AS based?

B.I.S. BYGG AS has its business address in Alta.

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.