BIZTRAC BETA
Manufacture of other parts and accessories for motor vehicles

URSUS SILENCE AS

Org. no. 927162539 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK −88,000
Incorporated 2021
Share capital NOK 110,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−88k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

URSUS SILENCE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927162539. The business is classified under manufacture of other parts and accessories for motor vehicles (NACE 29.320). The company was incorporated in 2021. Registered share capital is NOK 110,000, divided into 100 shares. The company's stated purpose is: “Investeringer i aksjer, andeler, samt alt hva hermed står i forbindelse, herunder deltakelse i andre virksomheter.”.

Key figures · 2024

Operating profit
NOK −8,000
Equity
NOK −88,000

Financial health · 2024

Liquidity
6.95
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.1%
Weak
Equity as a share of total capital

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

Who owns URSUS SILENCE AS?

URSUS INVEST AS
URSUS SILENCE AS
· NOK −8,000 profit

URSUS SILENCE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does URSUS SILENCE AS own?

URSUS SILENCE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about URSUS SILENCE AS

Who owns URSUS SILENCE AS?

URSUS INVEST AS is the largest registered owner, with 100.0%.

Where is URSUS SILENCE AS based?

URSUS SILENCE AS has its business address in Trondheim.

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.