BIZTRAC BETA
COMPANY REGISTER PROFILE
920320570 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

VÅR BOLIG AS

Org. no. 920320570 Limited company (AS) Ullensaker Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK 6,000
Equity NOK 11,000
Incorporated 2018
Share capital NOK 30,000

VÅR BOLIG AS is registered as a limited company in Ullensaker, Akershus with organisation number 920320570. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling og rådgivning samt kjøp og salg av aksjer.”.

Key figures · 2025

Operating profit
NOK 6,000
▲ +336 %
Equity
NOK 11,000
▲ +101 %
Est. value
NOK 14,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VÅR BOLIG AS?

VÅR BOLIG AS
· NOK 6,000 profit

VÅR BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÅR BOLIG AS

Who owns VÅR BOLIG AS?

HAS EIENDOM AS is the largest registered owner, with 100.0%.

Where is VÅR BOLIG AS based?

VÅR BOLIG AS has its business address in Jessheim.

Property

Business address c/o Espen Stene Sandshagan 15, 2067 Jessheim
Cadastral unit 3209-172/466/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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