BIZTRAC BETA
COMPANY REGISTER PROFILE
933151980 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

GENIALKRAFT INNOVATION AS

Org. no. 933151980 Limited company (AS) Rælingen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 40,000
Incorporated 2024
Share capital NOK 40,000

GENIALKRAFT INNOVATION AS is registered as a limited company in Rælingen, Akershus with organisation number 933151980. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Skape og utvikle tekniske bærekraftige fornybare energiløsninger, bidra inn i produksjon og markedsføring av selskapets produkter i tråd med FNs Bærekraftsmål 2030.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 40,000
Est. value
NOK 65,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 GENIALKRAFT INNOVATION AS?

SYDNEY TOUATON KOUAMÉ
GENIALKRAFT INNOVATION AS
NOK 0 rev. · NOK 0 profit

GENIALKRAFT INNOVATION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GENIALKRAFT INNOVATION AS

Who owns GENIALKRAFT INNOVATION AS?

SYDNEY TOUATON KOUAMÉ is the largest registered owner, with 100.0%.

What is the revenue of GENIALKRAFT INNOVATION AS?

GENIALKRAFT INNOVATION AS had revenue of NOK 0 in 2024.

Where is GENIALKRAFT INNOVATION AS based?

GENIALKRAFT INNOVATION AS has its business address in Løvenstad.

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.