BIZTRAC BETA
Computer consultancy and computer facilities management activities

PARITO AS

Org. no. 915553338 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 903,000
Equity NOK 1.7m
Incorporated 2015
Share capital NOK 190,000

PARITO AS is registered as a limited company in Bergen, Vestland with organisation number 915553338. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2015. Registered share capital is NOK 190,000, divided into 190 shares. The company's stated purpose is: “Konsulentvirksomhet, opplæring og andre tjenester innenfor IT, medvirke i andre selskaper innenfor samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 903,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 903,000
Equity
NOK 1.7m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns PARITO AS?

MARTIN LOMBNES HORVLI
PARITO AS
NOK 2.4m rev. · NOK 903,000 profit

PARITO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PARITO AS own?

PARITO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PARITO AS

Who owns PARITO AS?

MARTIN LOMBNES HORVLI is the largest registered owner, with 100.0%.

What is the revenue of PARITO AS?

PARITO AS had revenue of NOK 2.4m in 2025.

Who is the general manager of PARITO AS?

Martin Lombnes Horvli is registered as general manager of PARITO AS.

Where is PARITO AS based?

PARITO AS has its business address in Bergen.

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.