BIZTRAC BETA
Rental and leasing of other personal and household goods

EPOKEARKIVET AS

Org. no. 936626262 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-30.

EPOKEARKIVET AS is registered as a limited company in Oslo, Oslo with organisation number 936626262. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Utleie av klær, kostymer og utstyr. Konsulentvikrsomhet, kurs og reparasjon. Utvikling av utleie innen film og kultur. Kostymedesigntjenester og utvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 23,000
Est. value
NOK 32,000

Financial health · 2025

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

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

Who owns EPOKEARKIVET AS?

KAREN FABRITIUS GRAM
EPOKEARKIVET AS
NOK 0 rev. · NOK −8,000 profit

EPOKEARKIVET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EPOKEARKIVET AS

Who owns EPOKEARKIVET AS?

KAREN FABRITIUS GRAM is the largest registered owner, with 40.0%.

What is the revenue of EPOKEARKIVET AS?

EPOKEARKIVET AS had revenue of NOK 0 in 2025.

Where is EPOKEARKIVET AS based?

EPOKEARKIVET AS has its business address in Oslo.

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.