biztrac. BETA
COMPANY REGISTER PROFILE
961880823 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Bankrupt UPDATED 03.10.2026
⚠VISIONAIRE EIENDOM AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Rental and operating of own or leased real estate

VISIONAIRE EIENDOM AS

Org. no. 961880823 Limited company (AS) Tønsberg Incorporated 1991 Bankrupt
Operating profit NOK 0
Equity NOK −181,000
Incorporated 1991
Share capital NOK 972,000

Signals

1 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.

VISIONAIRE EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 961880823. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 972,000, divided into 972 shares. The company's stated purpose is: “Investere i fast eiendom.”.

Former names: PROJECT QUALITY SERVICE AS, VISIONAIRE AS

Key figures · 2024

Operating profit
NOK 0
Equity
NOK −181,000
▲ +0 %

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1632.5%
Weak
Equity as a share of total capital

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

Who owns VISIONAIRE EIENDOM AS?

VISIONAIRE ENERGY AS NO
VISIONAIRE EIENDOM AS
· NOK 0 profit

VISIONAIRE EIENDOM AS has 1 registered shareholder:

  • VISIONAIRE ENERGY AS 100.0%
All shareholders and roles →

Frequently asked questions about VISIONAIRE EIENDOM AS

Who owns VISIONAIRE EIENDOM AS?

VISIONAIRE ENERGY AS is the largest registered owner, with 100.0%.

Who is the general manager of VISIONAIRE EIENDOM AS?

Roar Berg is registered as general manager of VISIONAIRE EIENDOM AS.

Where is VISIONAIRE EIENDOM AS based?

VISIONAIRE EIENDOM AS has its business address in Tønsberg.

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.