BIZTRAC BETA
Business and other management consultancy activities

EIVIND JÅSUND AS

Org. no. 914733480 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 2.0m
Equity NOK 3.3m
Incorporated 2014
Share capital NOK 100,000

EIVIND JÅSUND AS is registered as a limited company in Bærum, Akershus with organisation number 914733480. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å drive investeringsvirksomhet, rådgivning og konsulentvirksomhet samt deltagelse i virksomhet relatert til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 2.0m
Equity
NOK 3.3m
Est. value
NOK 8.5m

Financial health · 2024

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

Who owns EIVIND JÅSUND AS?

EIVIND JÅSUND
EIVIND JÅSUND AS
NOK 3.9m rev. · NOK 2.0m profit

EIVIND JÅSUND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIVIND JÅSUND AS own?

EIVIND JÅSUND AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about EIVIND JÅSUND AS

Who owns EIVIND JÅSUND AS?

EIVIND JÅSUND is the largest registered owner, with 100.0%.

What is the revenue of EIVIND JÅSUND AS?

EIVIND JÅSUND AS had revenue of NOK 3.9m in 2024.

Who is the general manager of EIVIND JÅSUND AS?

Eivind Jåsund is registered as general manager of EIVIND JÅSUND AS.

Where is EIVIND JÅSUND AS based?

EIVIND JÅSUND AS has its business address in Høvik.

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.