BIZTRAC BETA
Business and other management consultancy activities

PERPETUAL AS

Org. no. 913521919 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −59,000
Equity NOK 64,000
Incorporated 2014
Share capital NOK 280,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−59k kr).

PERPETUAL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913521919. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 280,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer, obligasjoner og andre finansaktiva, og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −59,000
Equity
NOK 64,000
Est. value
NOK 104,000

Financial health · 2024

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

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

Who owns PERPETUAL AS?

JULIUSSEN INVEST AS
PERPETUAL AS
NOK 0 rev. · NOK −59,000 profit

PERPETUAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PERPETUAL AS own?

PERPETUAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PERPETUAL AS

Who owns PERPETUAL AS?

JULIUSSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of PERPETUAL AS?

PERPETUAL AS had revenue of NOK 0 in 2024.

Where is PERPETUAL AS based?

PERPETUAL AS has its business address in Trondheim.

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.