biztrac. BETA
COMPANY REGISTER PROFILE
926419579 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of textiles

CREATIV SOLSKJERMING AS

Org. no. 926419579 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 7.5m
Operating profit NOK 509,000
Equity NOK 1.7m
Incorporated 2021
Employees 6
Share capital NOK 30,000

CREATIV SOLSKJERMING AS is registered as a limited company in Oslo, Oslo with organisation number 926419579. The business is classified under wholesale of textiles (NACE 46.410). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Solskjerming.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.5m in revenue and NOK 509,000 in operating profit.

Former names: MIDGARD CAPITAL AS

Key figures · 2025

Revenue
NOK 7.5m
▼ −4 %
Operating profit
NOK 509,000
▲ +29 %
Equity
NOK 1.7m
▲ +22 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
2.10
Very good
Current assets ÷ current liabilities
Profitability
17.5%
Very good
Return on total assets
Solidity
52.9%
Very good
Equity as a share of total capital

Who owns CREATIV SOLSKJERMING AS?

CREATIV SOLSKJERMING AS
NOK 7.5m rev. · NOK 509,000 profit

CREATIV SOLSKJERMING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CREATIV SOLSKJERMING AS

Who owns CREATIV SOLSKJERMING AS?

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

What is the revenue of CREATIV SOLSKJERMING AS?

CREATIV SOLSKJERMING AS had revenue of NOK 7.5m in 2025.

Who is the general manager of CREATIV SOLSKJERMING AS?

Bjørn-Morten Granum is registered as general manager of CREATIV SOLSKJERMING AS.

Where is CREATIV SOLSKJERMING AS based?

CREATIV SOLSKJERMING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.