BIZTRAC BETA
Intermediation service activities for specialised retail sale

INGUNN JEPPESTØL AS

Org. no. 913098218 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 135,000
Operating profit NOK 6,000
Equity NOK 501,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-29 Adresseendring registrert 2026-07-29.

INGUNN JEPPESTØL AS is registered as a limited company in Bergen, Vestland with organisation number 913098218. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Agentvirksomhet for salg av hårprodukter. Kurs og konferansevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 135,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 135,000
Operating profit
NOK 6,000
Equity
NOK 501,000
Est. value
NOK 273,000

Financial health · 2025

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

Who owns INGUNN JEPPESTØL AS?

INGUNN JEPPESTØL
INGUNN JEPPESTØL AS
NOK 135,000 rev. · NOK 6,000 profit

INGUNN JEPPESTØL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INGUNN JEPPESTØL AS

Who owns INGUNN JEPPESTØL AS?

INGUNN JEPPESTØL is the largest registered owner, with 100.0%.

What is the revenue of INGUNN JEPPESTØL AS?

INGUNN JEPPESTØL AS had revenue of NOK 135,000 in 2025.

Who is the general manager of INGUNN JEPPESTØL AS?

Ingunn Jeppestøl is registered as general manager of INGUNN JEPPESTØL AS.

Where is INGUNN JEPPESTØL AS based?

INGUNN JEPPESTØL AS has its business address in Mathopen.

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.