BIZTRAC BETA
Rental and operating of own or leased real estate

J KARLSEN EIENDOM AS

Org. no. 871201722 Limited company (AS) Vestre Toten Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 3.8m
Equity NOK 2.4m
Incorporated 1994
Share capital NOK 420,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

J KARLSEN EIENDOM AS is registered as a limited company in Vestre Toten, Innlandet with organisation number 871201722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 420,000, divided into 420 shares. The company's stated purpose is: “Eie og drive fast eiendom, herunder eie aksjer og andeler i andre eiendomsselskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 3.8m in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK 3.8m
Equity
NOK 2.4m
Est. value
NOK 8.1m

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.7%
Weak
Equity as a share of total capital

Who owns J KARLSEN EIENDOM AS?

PROGAR AS
J KARLSEN EIENDOM AS
NOK 5.5m rev. · NOK 3.8m profit

J KARLSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

J KARLSEN EIENDOM AS er morselskap for 7 datterselskaper:

Frequently asked questions about J KARLSEN EIENDOM AS

Who owns J KARLSEN EIENDOM AS?

PROGAR AS is the largest registered owner, with 100.0%.

What is the revenue of J KARLSEN EIENDOM AS?

J KARLSEN EIENDOM AS had revenue of NOK 5.5m in 2025.

Where is J KARLSEN EIENDOM AS based?

J KARLSEN EIENDOM AS has its business address in Raufoss.

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.