BIZTRAC BETA
COMPANY REGISTER PROFILE
933029522 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
General cleaning of buildings

VIPADA-RENHOLD AS

Org. no. 933029522 Limited company (AS) Færder Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −222,000
Equity NOK −143,000
Incorporated 2024
Employees 6
Share capital NOK 120,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−143k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−222k kr).

VIPADA-RENHOLD AS is registered as a limited company in Færder, Vestfold with organisation number 933029522. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2024 and has 6 registered employees. Registered share capital is NOK 120,000, divided into 400 shares. The company's stated purpose is: “Renhold og salg av produkter og tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −222,000
Equity
NOK −143,000

Financial health · 2024

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

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

Who owns VIPADA-RENHOLD AS?

JAN PETTER ANDERSEN
VIPADA-RENHOLD AS
· NOK −222,000 profit

VIPADA-RENHOLD AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIPADA-RENHOLD AS

Who owns VIPADA-RENHOLD AS?

JAN PETTER ANDERSEN is the largest registered owner, with 50.0%.

Who is the general manager of VIPADA-RENHOLD AS?

Jan Petter Andersen is registered as general manager of VIPADA-RENHOLD AS.

Where is VIPADA-RENHOLD AS based?

VIPADA-RENHOLD AS has its business address in Nøtterøy.

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.