BIZTRAC BETA
Rental and operating of own or leased real estate

CUSTO AS

Org. no. 961954606 Limited company (AS) Oslo Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 1.9m
Equity NOK 11.1m
Incorporated 1991
Share capital NOK 1.5m

CUSTO AS is registered as a limited company in Oslo, Oslo with organisation number 961954606. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 1.5m, divided into 900 shares. The company's stated purpose is: “Produksjon, handel, ervervelse og drift av faste eiendommer, skipsfart og utnyttelse av naturfore- komster, finansieringsvirksomhet samt annen virk- somhet i forbindelse med slike formål. Selskapet kan ved aksjetegning eller på annen måte, herunder ved långivning, interessere seg i andre foretagender med samme eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 1.9m
Equity
NOK 11.1m
Est. value
NOK 11.3m

Financial health · 2024

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

Who owns CUSTO AS?

KEVLAR INVEST AS
CUSTO AS
NOK 4.4m rev. · NOK 1.9m profit

CUSTO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CUSTO AS own?

CUSTO AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about CUSTO AS

Who owns CUSTO AS?

KEVLAR INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of CUSTO AS?

CUSTO AS had revenue of NOK 4.4m in 2024.

Where is CUSTO AS based?

CUSTO 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.