biztrac. BETA
COMPANY REGISTER PROFILE
921749260 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠VASSHØLET AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and operating of own or leased real estate

VASSHØLET AS

Org. no. 921749260 Limited company (AS) Nannestad Incorporated 2018 In liquidation
Revenue 2025 NOK 270,000
Operating profit NOK 179,000
Equity NOK 672,000
Incorporated 2018
Share capital NOK 500,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

VASSHØLET AS is registered as a limited company in Nannestad, Akershus with organisation number 921749260. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Eiendomsbesittelse, forvaltning, drift og utleie samt deltagelse i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 270,000 in revenue and NOK 179,000 in operating profit.

Key figures · 2025

Revenue
NOK 270,000
▼ −36 %
Operating profit
NOK 179,000
▼ −46 %
Equity
NOK 672,000
▼ −9 %

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
3.8%
Weak
Return on total assets
Solidity
14.2%
Satisfactory
Equity as a share of total capital

Who owns VASSHØLET AS?

VASSHØLET AS
NOK 270,000 rev. · NOK 179,000 profit

VASSHØLET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VASSHØLET AS

Who owns VASSHØLET AS?

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

What is the revenue of VASSHØLET AS?

VASSHØLET AS had revenue of NOK 270,000 in 2025.

Where is VASSHØLET AS based?

VASSHØLET AS has its business address in Holter.

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.