BIZTRAC BETA
General medical practice activities

JUJEPA AS

Org. no. 918668616 Limited company (AS) Sunnfjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 178,000
Equity NOK −83,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−83k kr).

JUJEPA AS is registered as a limited company in Sunnfjord, Vestland with organisation number 918668616. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Legevirksomhet, herunder legevakt, kurs og undervisning, investering og deltakelse i eiendom og andre selskaper, samt alt annet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 178,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 178,000
Equity
NOK −83,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.2%
Weak
Equity as a share of total capital

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

Who owns JUJEPA AS?

JENS CHRISTIAN FABER-ROD
JUJEPA AS
NOK 3.4m rev. · NOK 178,000 profit

JUJEPA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JUJEPA AS

Who owns JUJEPA AS?

JENS CHRISTIAN FABER-ROD is the largest registered owner, with 100.0%.

What is the revenue of JUJEPA AS?

JUJEPA AS had revenue of NOK 3.4m in 2025.

Who is the general manager of JUJEPA AS?

Jens Christian Faber-Rod is registered as general manager of JUJEPA AS.

Where is JUJEPA AS based?

JUJEPA AS has its business address in Førde.

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.