BIZTRAC BETA
Interior design activities

ASTOR DESIGN AS

Org. no. 815330722 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 17,000
Operating profit NOK 9,000
Equity NOK −52,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−52k kr).

ASTOR DESIGN AS is registered as a limited company in Bærum, Akershus with organisation number 815330722. The business is classified under interior design activities (NACE 74.130). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie, kjøpe og administrere aksjer i selskaper. Kjøp / salg av aksjer og alt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 17,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 17,000
Operating profit
NOK 9,000
Equity
NOK −52,000
Est. value
NOK 40,000

Financial health · 2024

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-211.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ASTOR DESIGN AS?

LINDA ASTOR
ASTOR DESIGN AS
NOK 17,000 rev. · NOK 9,000 profit

ASTOR DESIGN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ASTOR DESIGN AS own?

ASTOR DESIGN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ASTOR DESIGN AS

Who owns ASTOR DESIGN AS?

LINDA ASTOR is the largest registered owner, with 100.0%.

What is the revenue of ASTOR DESIGN AS?

ASTOR DESIGN AS had revenue of NOK 17,000 in 2024.

Where is ASTOR DESIGN AS based?

ASTOR DESIGN AS has its business address in Hosle.

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.