BIZTRAC BETA
Architectural activities

YSADESIGN AS

Org. no. 853606162 Limited company (AS) Oslo Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 57.6m
Operating profit NOK 9.5m
Equity NOK 15.6m
Incorporated 1989
Employees 26
Share capital NOK 1.2m

YSADESIGN AS is registered as a limited company in Oslo, Oslo with organisation number 853606162. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1989 and has 26 registered employees. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Arkitekt-/forretningsvirksomhet av enhver art samt deltakelse i slik virksomhet gjennom aksje- besittelse eller på annen måte, eiendomsdrift samt forvaltning av egne midler.”. The most recent filed accounts, for the 2025 financial year, show NOK 57.6m in revenue and NOK 9.5m in operating profit.

Key figures · 2025

Revenue
NOK 57.6m
Operating profit
NOK 9.5m
Equity
NOK 15.6m
Est. value
NOK 54.9m

Financial health · 2025

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

Who owns YSADESIGN AS?

TROND SIGURDSEN AS
YSADESIGN AS
NOK 57.6m rev. · NOK 9.5m profit

YSADESIGN AS has 6 registered shareholders:

All shareholders and roles →

Which companies does YSADESIGN AS own?

YSADESIGN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about YSADESIGN AS

Who owns YSADESIGN AS?

TROND SIGURDSEN AS is the largest registered owner, with 17.5%.

What is the revenue of YSADESIGN AS?

YSADESIGN AS had revenue of NOK 57.6m in 2025.

Who is the general manager of YSADESIGN AS?

Anne Mari Gullikstad is registered as general manager of YSADESIGN AS.

Where is YSADESIGN AS based?

YSADESIGN 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 15.06.2026.

Report a problem

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