BIZTRAC BETA
Site preparation

BISTO ENTREPRENØR AS

Org. no. 920209270 Limited company (AS) Indre Østfold Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 31.5m
Operating profit NOK 423,000
Equity NOK 1.4m
Incorporated 2017
Employees 22
Share capital NOK 300,000

BISTO ENTREPRENØR AS is registered as a limited company in Indre Østfold, Østfold with organisation number 920209270. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017 and has 22 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Entreprenørvirksomhet innen grunnarbeider. Utgraving og flytting av masse innen vei og anlegg og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 31.5m in revenue and NOK 423,000 in operating profit.

Key figures · 2025

Revenue
NOK 31.5m
Operating profit
NOK 423,000
Equity
NOK 1.4m
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns BISTO ENTREPRENØR AS?

STRØMS HOLDING INVEST AS
BISTO ENTREPRENØR AS
NOK 31.5m rev. · NOK 423,000 profit

BISTO ENTREPRENØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BISTO ENTREPRENØR AS

Who owns BISTO ENTREPRENØR AS?

STRØMS HOLDING INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BISTO ENTREPRENØR AS?

BISTO ENTREPRENØR AS had revenue of NOK 31.5m in 2025.

Who is the general manager of BISTO ENTREPRENØR AS?

Bjørn Ole Furulund Strøm is registered as general manager of BISTO ENTREPRENØR AS.

Where is BISTO ENTREPRENØR AS based?

BISTO ENTREPRENØR AS has its business address in Spydeberg.

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.