BIZTRAC BETA
Office administrative and support activities

PERAKO AS

Org. no. 986565809 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −4.0m
Equity NOK −7.6m
Incorporated 2004
Share capital NOK 102,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−7,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,0 mill kr).

PERAKO AS is registered as a limited company in Oslo, Oslo with organisation number 986565809. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2004. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Kjøp av fordringer, fakturaadministrasjon og beslektede tjenester såvel i egen regi som ved deltagelse i andre selskap med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −4.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −4.0m
Equity
NOK −7.6m

Financial health · 2024

Liquidity
75.48
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-90.1%
Weak
Equity as a share of total capital

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

Who owns PERAKO AS?

TOMMY JØNSSON
PERAKO AS
NOK 1.1m rev. · NOK −4.0m profit

PERAKO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERAKO AS

Who owns PERAKO AS?

TOMMY JØNSSON is the largest registered owner, with 100.0%.

What is the revenue of PERAKO AS?

PERAKO AS had revenue of NOK 1.1m in 2024.

Who is the general manager of PERAKO AS?

Tommy Jønsson is registered as general manager of PERAKO AS.

Where is PERAKO AS based?

PERAKO AS has its business address in Oslo.

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.