BIZTRAC BETA
Business and other management consultancy activities

LOCO INVEST AS

Org. no. 989252658 Limited company (AS) Klepp Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 813,000
Operating profit NOK 507,000
Equity NOK 17.9m
Incorporated 2005
Share capital NOK 1.1m

LOCO INVEST AS is registered as a limited company in Klepp, Rogaland with organisation number 989252658. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 1.1m, divided into 1 shares. The company's stated purpose is: “Investeringer i verdipapirer og selskapsandeler, konsulenttjenester innenfor økonomi og bedriftsstyring, samt hva hermed kommer i forbindelse”. The most recent filed accounts, for the 2024 financial year, show NOK 813,000 in revenue and NOK 507,000 in operating profit.

Key figures · 2024

Revenue
NOK 813,000
Operating profit
NOK 507,000
Equity
NOK 17.9m
Est. value
NOK 11.2m

Financial health · 2024

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

Who owns LOCO INVEST AS?

LIVAR OHMA
LOCO INVEST AS
NOK 813,000 rev. · NOK 507,000 profit

LOCO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOCO INVEST AS own?

LOCO INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about LOCO INVEST AS

Who owns LOCO INVEST AS?

LIVAR OHMA is the largest registered owner, with 100.0%.

What is the revenue of LOCO INVEST AS?

LOCO INVEST AS had revenue of NOK 813,000 in 2024.

Who is the general manager of LOCO INVEST AS?

Livar Ohma is registered as general manager of LOCO INVEST AS.

Where is LOCO INVEST AS based?

LOCO INVEST AS has its business address in Kleppe.

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.