BIZTRAC BETA
General cleaning of buildings

GAJA PROFF AS

Org. no. 918816593 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −11,000
Equity NOK 15,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

GAJA PROFF AS is registered as a limited company in Oslo, Oslo with organisation number 918816593. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Renhold tjenester, oppføring og rehabilitering av bygg, arkitekt tjenester samt salg av byggevarer og verktøy. Import og eksport av varer og tjenester. Investering i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −11,000
Equity
NOK 15,000
Est. value
NOK 1.2m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GAJA PROFF AS?

ANNA PRZYCHODA
GAJA PROFF AS
NOK 1.9m rev. · NOK −11,000 profit

GAJA PROFF AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GAJA PROFF AS

Who owns GAJA PROFF AS?

ANNA PRZYCHODA is the largest registered owner, with 80.0%.

What is the revenue of GAJA PROFF AS?

GAJA PROFF AS had revenue of NOK 1.9m in 2025.

Who is the general manager of GAJA PROFF AS?

Agnieszka Choluj is registered as general manager of GAJA PROFF AS.

Where is GAJA PROFF AS based?

GAJA PROFF 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.