BIZTRAC BETA
Motion picture, video and television programme production activities

KREATIV KI AS

Org. no. 833451502 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 281,000
Operating profit NOK 27,000
Equity NOK 45,000
Incorporated 2024
Share capital NOK 30,000

KREATIV KI AS is registered as a limited company in Bærum, Akershus with organisation number 833451502. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kreativ KI skal tilby konsulenttjenester og utvikle skreddersydde KI-løsninger spesialtilpasset film.”. The most recent filed accounts, for the 2024 financial year, show NOK 281,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2024

Revenue
NOK 281,000
Operating profit
NOK 27,000
Equity
NOK 45,000
Est. value
NOK 178,000

Financial health · 2024

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

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

Who owns KREATIV KI AS?

JAN CHRISTIAN VIVE FRUGÅRD
KREATIV KI AS
NOK 281,000 rev. · NOK 27,000 profit

KREATIV KI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KREATIV KI AS

Who owns KREATIV KI AS?

JAN CHRISTIAN VIVE FRUGÅRD is the largest registered owner, with 100.0%.

What is the revenue of KREATIV KI AS?

KREATIV KI AS had revenue of NOK 281,000 in 2024.

Who is the general manager of KREATIV KI AS?

Jan Christian Vive Frugård is registered as general manager of KREATIV KI AS.

Where is KREATIV KI AS based?

KREATIV KI AS has its business address in Blommenholm.

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.