BIZTRAC BETA
Business and other management consultancy activities

JØRGEN AASS AS

Org. no. 917622159 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −68,000
Equity NOK 7,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−68k kr).

JØRGEN AASS AS is registered as a limited company in Bærum, Akershus with organisation number 917622159. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innenfor opplæring, ledelse og tjenesteyting knyttet til prosjekter for tilrettelegging for fotgjengere og store folkemengder, trafikk og transportplanlegging, ledelse og gjennomføring av events. Samt deltagelse i andre virksomheter og investeringer”.

Key figures · 2024

Operating profit
NOK −68,000
Equity
NOK 7,000
Est. value
NOK 12,000

Financial health · 2024

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

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

Who owns JØRGEN AASS AS?

JØRGEN AASS
JØRGEN AASS AS
· NOK −68,000 profit

JØRGEN AASS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JØRGEN AASS AS own?

JØRGEN AASS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JØRGEN AASS AS

Who owns JØRGEN AASS AS?

JØRGEN AASS is the largest registered owner, with 100.0%.

Who is the general manager of JØRGEN AASS AS?

Jørgen Aass is registered as general manager of JØRGEN AASS AS.

Where is JØRGEN AASS AS based?

JØRGEN AASS AS has its business address in Vøyenenga.

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.