BIZTRAC BETA
Wholesale of information and communication equipment

PERICO AS

Org. no. 934603818 Limited company (AS) Nordre Follo Incorporated 1983 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 1.2m
Equity NOK 900,000
Incorporated 1983
Share capital NOK 100,000

PERICO AS is registered as a limited company in Nordre Follo, Akershus with organisation number 934603818. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1983. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Handel, produksjon, agentvirksomhet, kjøp og salg av skip og skipsparter, entreprenørvirksomhet, kjøp og salg av verdipapirer, samt ved aksjeteg- ning eller på annen måte delta i eller overta, finansiere, administrere og lede selskaper med virksomhet som nevnt over.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 1.2m
Equity
NOK 900,000
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns PERICO AS?

PERICO HOLDING AS
PERICO AS
NOK 3.3m rev. · NOK 1.2m profit

PERICO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERICO AS

Who owns PERICO AS?

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

What is the revenue of PERICO AS?

PERICO AS had revenue of NOK 3.3m in 2025.

Who is the general manager of PERICO AS?

Per Johan Spilling is registered as general manager of PERICO AS.

Where is PERICO AS based?

PERICO AS has its business address in Trollåsen.

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.