biztrac. BETA
COMPANY REGISTER PROFILE
988622133 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

JOGU AS

Org. no. 988622133 Limited company (AS) Lindesnes Incorporated 2005 Active
Revenue 2025 NOK 384,000
Operating profit NOK −151,000
Equity NOK 8.0m
Incorporated 2005
Share capital NOK 2.9m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−151k kr).

JOGU AS is registered as a limited company in Lindesnes, Agder with organisation number 988622133. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.9m, divided into 2250 shares. The company's stated purpose is: “Utleie av leiligheter og ferieleiligheter, eiendomsutvikling, samt alt hva som der står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskap eller foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 384,000 in revenue and NOK −151,000 in operating profit.

Key figures · 2025

Revenue
NOK 384,000
▼ −98 %
Operating profit
NOK −151,000
▼ −101 %
Equity
NOK 8.0m
▼ −1 %
Est. value
NOK 14.7m

Financial health · 2025

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.7%
Not satisfactory
Return on total assets
Solidity
44.6%
Very good
Equity as a share of total capital

Who owns JOGU AS?

JOGU AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOGU AS

Who owns JOGU AS?

A.G.O HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of JOGU AS?

JOGU AS had revenue of NOK 384,000 in 2025.

Who is the general manager of JOGU AS?

Gustav Olsen is registered as general manager of JOGU AS.

Where is JOGU AS based?

JOGU AS has its business address in Mandal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.