BIZTRAC BETA
Computer programming activities

KB CREATIVE AS

Org. no. 927376989 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 49,000
Equity NOK −119,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−119k kr).

KB CREATIVE AS is registered as a limited company in Oslo, Oslo with organisation number 927376989. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av digitale tjenester som oppsett av nettsider, nettbutikk og visuell profil. Salg av varer med eget design over nett.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 49,000
Equity
NOK −119,000
Est. value
NOK 554,000

Financial health · 2025

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

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

Who owns KB CREATIVE AS?

KATINKA JEE HEE USTAD
KB CREATIVE AS
NOK 1.2m rev. · NOK 49,000 profit

KB CREATIVE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KB CREATIVE AS

Who owns KB CREATIVE AS?

KATINKA JEE HEE USTAD is the largest registered owner, with 50.0%.

What is the revenue of KB CREATIVE AS?

KB CREATIVE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of KB CREATIVE AS?

Brikt Julian Utstrand Sagbakken is registered as general manager of KB CREATIVE AS.

Where is KB CREATIVE AS based?

KB CREATIVE 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.