BIZTRAC BETA
Accounting and bookkeeping

KLOK REGNSKAP AS

Org. no. 933630684 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 35,000
Operating profit NOK −5,000
Equity NOK 59,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

KLOK REGNSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 933630684. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Regnskapsførervirksomhet, økonomisk rådgivning, salg av administrative tjenester og annen virksomhet i naturlig forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 35,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 35,000
Operating profit
NOK −5,000
Equity
NOK 59,000
Est. value
NOK 65,000

Financial health · 2024

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

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

Who owns KLOK REGNSKAP AS?

GEZIM HAXHA
KLOK REGNSKAP AS
NOK 35,000 rev. · NOK −5,000 profit

KLOK REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLOK REGNSKAP AS

Who owns KLOK REGNSKAP AS?

GEZIM HAXHA is the largest registered owner, with 100.0%.

What is the revenue of KLOK REGNSKAP AS?

KLOK REGNSKAP AS had revenue of NOK 35,000 in 2024.

Who is the general manager of KLOK REGNSKAP AS?

Sadik Haxha is registered as general manager of KLOK REGNSKAP AS.

Where is KLOK REGNSKAP AS based?

KLOK REGNSKAP 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.