BIZTRAC BETA
Construction of residential and non-residential buildings

VISJONSBYGG AS

Org. no. 912174107 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK −853,000
Equity NOK 421,000
Incorporated 2013
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−853k kr).

VISJONSBYGG AS is registered as a limited company in Bærum, Akershus with organisation number 912174107. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring, ombygging, reparasjon og vedlikehold av alle typer bygninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK −853,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK −853,000
Equity
NOK 421,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns VISJONSBYGG AS?

JØ HOLDING AS
VISJONSBYGG AS
NOK 3.0m rev. · NOK −853,000 profit

VISJONSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VISJONSBYGG AS

Who owns VISJONSBYGG AS?

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

What is the revenue of VISJONSBYGG AS?

VISJONSBYGG AS had revenue of NOK 3.0m in 2024.

Who is the general manager of VISJONSBYGG AS?

Jonas Bo Ivan Östergren is registered as general manager of VISJONSBYGG AS.

Where is VISJONSBYGG AS based?

VISJONSBYGG AS has its business address in Østerås.

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.