BIZTRAC BETA
Industrial product and fashion design activities

JFK EYEWEAR AS

Org. no. 925371815 Limited company (AS) Kristiansand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 37,000
Operating profit NOK −75,000
Equity NOK −43,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−43k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−75k kr).

JFK EYEWEAR AS is registered as a limited company in Kristiansand, Agder with organisation number 925371815. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Design og produksjon av briller og annet som naturlig hører sammen med dette, herunder delta i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 37,000 in revenue and NOK −75,000 in operating profit.

Key figures · 2025

Revenue
NOK 37,000
Operating profit
NOK −75,000
Equity
NOK −43,000

Financial health · 2024

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

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

Who owns JFK EYEWEAR AS?

KARI SANDSTAA
JFK EYEWEAR AS
NOK 37,000 rev. · NOK −75,000 profit

JFK EYEWEAR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JFK EYEWEAR AS

Who owns JFK EYEWEAR AS?

KARI SANDSTAA is the largest registered owner, with 50.0%.

What is the revenue of JFK EYEWEAR AS?

JFK EYEWEAR AS had revenue of NOK 37,000 in 2025.

Where is JFK EYEWEAR AS based?

JFK EYEWEAR AS has its business address in Kristiansand S.

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.