BIZTRAC BETA
Graphic design and visual communication activities

KYLLINGSTAD DESIGN AS

Org. no. 916930607 Limited company (AS) Evje Og Hornnes Incorporated 2016 Active
Ownership graph ↗
Revenue 2023 NOK 1.4m
Operating profit NOK 409,000
Equity NOK 595,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

KYLLINGSTAD DESIGN AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 916930607. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tjenester innen design, reklame og markedsrådgivning.”. The most recent filed accounts, for the 2023 financial year, show NOK 1.4m in revenue and NOK 409,000 in operating profit.

Key figures · 2023

Revenue
NOK 1.4m
Operating profit
NOK 409,000
Equity
NOK 595,000
Est. value
NOK 1.7m

Financial health · 2023

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

Who owns KYLLINGSTAD DESIGN AS?

CECILIE KYLLINGSTAD
KYLLINGSTAD DESIGN AS
NOK 1.4m rev. · NOK 409,000 profit

KYLLINGSTAD DESIGN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KYLLINGSTAD DESIGN AS own?

KYLLINGSTAD DESIGN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KYLLINGSTAD DESIGN AS

Who owns KYLLINGSTAD DESIGN AS?

CECILIE KYLLINGSTAD is the largest registered owner, with 100.0%.

What is the revenue of KYLLINGSTAD DESIGN AS?

KYLLINGSTAD DESIGN AS had revenue of NOK 1.4m in 2023.

Where is KYLLINGSTAD DESIGN AS based?

KYLLINGSTAD DESIGN AS has its business address in Evje.

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.