BIZTRAC BETA
Uoppgitt

RAPIDINVEST AS

Org. no. 955220307 Limited company (AS) Lier Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 551,000
Incorporated 1989
Share capital NOK 89,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

RAPIDINVEST AS is registered as a limited company in Lier, Buskerud with organisation number 955220307. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1989. Registered share capital is NOK 89,000, divided into 2550 shares. The company's stated purpose is: “Produksjon, kjøp og salg av planter og grønnsaker, og hva derved står i forbindelse, samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 551,000
Est. value
NOK 648,000

Financial health · 2025

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

Who owns RAPIDINVEST AS?

HANS ERIK FUGLERUD
RAPIDINVEST AS
NOK 0 rev. · NOK −14,000 profit

RAPIDINVEST AS has 6 registered shareholders:

All shareholders and roles →

Which companies does RAPIDINVEST AS own?

RAPIDINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RAPIDINVEST AS

Who owns RAPIDINVEST AS?

HANS ERIK FUGLERUD is the largest registered owner, with 33.3%.

What is the revenue of RAPIDINVEST AS?

RAPIDINVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of RAPIDINVEST AS?

Jan Rune Fuglerud is registered as general manager of RAPIDINVEST AS.

Where is RAPIDINVEST AS based?

RAPIDINVEST AS has its business address in Lier.

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.