BIZTRAC BETA
COMPANY REGISTER PROFILE
931949705 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SIERRA CAPITAL AS

Org. no. 931949705 Limited company (AS) Hole Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 17,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

SIERRA CAPITAL AS is registered as a limited company in Hole, Buskerud with organisation number 931949705. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Økonomisk investering av ethvert slag, herunder investeringer i fast eiendom, aksjer og andre verdipapirer, deltakelse i andre virksomheter og hva dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −17,000
Equity
NOK 17,000
Est. value
NOK 94,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.1%
Weak
Equity as a share of total capital

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

Who owns SIERRA CAPITAL AS?

SIERRA CAPITAL AS
· NOK −17,000 profit

SIERRA CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIERRA CAPITAL AS own?

SIERRA CAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIERRA CAPITAL AS

Who owns SIERRA CAPITAL AS?

OLE MARTIN JEEVANTHA BOSÅEN is the largest registered owner, with 100.0%.

Who is the general manager of SIERRA CAPITAL AS?

Ole Martin Jeevantha Bosåen is registered as general manager of SIERRA CAPITAL AS.

Where is SIERRA CAPITAL AS based?

SIERRA CAPITAL AS has its business address in Krokkleiva.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

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