BIZTRAC BETA
Operation of sports facilities

JAR ISFORUM AS

Org. no. 992827025 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 11.4m
Operating profit NOK 496,000
Equity NOK 888,000
Incorporated 2008
Employees 9
Share capital NOK 100,000

Signals

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

JAR ISFORUM AS is registered as a limited company in Bærum, Akershus with organisation number 992827025. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2008 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av idrettshall.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.4m in revenue and NOK 496,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.4m
Operating profit
NOK 496,000
Equity
NOK 888,000
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.80
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.8%
Good
Equity as a share of total capital

Who owns JAR ISFORUM AS?

JAR ISHALL AS
JAR ISFORUM AS
NOK 11.4m rev. · NOK 496,000 profit

JAR ISFORUM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JAR ISFORUM AS er morselskap for 2 datterselskaper:

Frequently asked questions about JAR ISFORUM AS

Who owns JAR ISFORUM AS?

JAR ISHALL AS is the largest registered owner, with 100.0%.

What is the revenue of JAR ISFORUM AS?

JAR ISFORUM AS had revenue of NOK 11.4m in 2025.

Who is the general manager of JAR ISFORUM AS?

Bjørn Oskar Libæk is registered as general manager of JAR ISFORUM AS.

Where is JAR ISFORUM AS based?

JAR ISFORUM AS has its business address in Jar.

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.