BIZTRAC BETA
Retail sale of textiles

KREAKTIV SANDNES AS

Org. no. 935980860 Limited company (AS) Sandnes Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 16.4m
Operating profit NOK 216,000
Equity NOK 4.1m
Incorporated 1984
Employees 18
Share capital NOK 940,000

Signals

1 flags
  • Nylig endring 2026-07-20 Adresseendring registrert 2026-07-20.

KREAKTIV SANDNES AS is registered as a limited company in Sandnes, Rogaland with organisation number 935980860. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 1984 and has 18 registered employees. Registered share capital is NOK 940,000, divided into 9400 shares. The company's stated purpose is: “Handel og agentur og dermed det som er forbundet, bl.a. også adgang til å delta i andre selskaper i tilsvarende bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.4m in revenue and NOK 216,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.4m
Operating profit
NOK 216,000
Equity
NOK 4.1m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
1.71
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.7%
Very good
Equity as a share of total capital

Who owns KREAKTIV SANDNES AS?

WIGG AS
KREAKTIV SANDNES AS
NOK 16.4m rev. · NOK 216,000 profit

KREAKTIV SANDNES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KREAKTIV SANDNES AS

Who owns KREAKTIV SANDNES AS?

WIGG AS is the largest registered owner, with 100.0%.

What is the revenue of KREAKTIV SANDNES AS?

KREAKTIV SANDNES AS had revenue of NOK 16.4m in 2024.

Who is the general manager of KREAKTIV SANDNES AS?

Gro Tjøstheim is registered as general manager of KREAKTIV SANDNES AS.

Where is KREAKTIV SANDNES AS based?

KREAKTIV SANDNES AS has its business address in Sandnes.

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.