BIZTRAC BETA
Rental and operating of own or leased real estate

GDO & JACKI AS

Org. no. 832469122 Limited company (AS) Vefsn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 850,000
Operating profit NOK 413,000
Equity NOK 155,000
Incorporated 2023
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GDO & JACKI AS is registered as a limited company in Vefsn, Nordland with organisation number 832469122. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 30 shares. The company's stated purpose is: “Utleie av forretnings- og kontorbygg, herunder det som står i naturlig tilknytning.”. The most recent filed accounts, for the 2025 financial year, show NOK 850,000 in revenue and NOK 413,000 in operating profit.

Key figures · 2025

Revenue
NOK 850,000
Operating profit
NOK 413,000
Equity
NOK 155,000
Est. value
NOK 812,000

Financial health · 2025

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.5%
Not satisfactory
Equity as a share of total capital

Who owns GDO & JACKI AS?

PIRI HOLDING AS
GDO & JACKI AS
NOK 850,000 rev. · NOK 413,000 profit

GDO & JACKI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GDO & JACKI AS

Who owns GDO & JACKI AS?

PIRI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GDO & JACKI AS?

GDO & JACKI AS had revenue of NOK 850,000 in 2025.

Who is the general manager of GDO & JACKI AS?

Ares Piri is registered as general manager of GDO & JACKI AS.

Where is GDO & JACKI AS based?

GDO & JACKI AS has its business address in Mosjøen.

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.