BIZTRAC BETA
Computer programming activities

KICKIT AS

Org. no. 817093442 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 25,000
Operating profit NOK −30,000
Equity NOK 27,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

KICKIT AS is registered as a limited company in Haugesund, Rogaland with organisation number 817093442. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og programmering av alle typer applikasjoner og system rettet mot mobil, data og internett, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 25,000 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 25,000
Operating profit
NOK −30,000
Equity
NOK 27,000
Est. value
NOK 54,000

Financial health · 2024

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

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

Who owns KICKIT AS?

KAROLINE ASPAAS KVINNESLAND
KICKIT AS
NOK 25,000 rev. · NOK −30,000 profit

KICKIT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KICKIT AS own?

KICKIT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KICKIT AS

Who owns KICKIT AS?

KAROLINE ASPAAS KVINNESLAND is the largest registered owner, with 50.0%.

What is the revenue of KICKIT AS?

KICKIT AS had revenue of NOK 25,000 in 2024.

Where is KICKIT AS based?

KICKIT AS has its business address in Haugesund.

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.