BIZTRAC BETA
Computer consultancy and computer facilities management activities

JABA AS

Org. no. 931273329 Limited company (AS) Skien Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 212,000
Equity NOK 618,000
Incorporated 2023
Share capital NOK 30,000

JABA AS is registered as a limited company in Skien, Telemark with organisation number 931273329. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen konsulentvirksomhet - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 212,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 212,000
Equity
NOK 618,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns JABA AS?

JANN ROGER BARLAUP-ÅSNES
JABA AS
NOK 3.2m rev. · NOK 212,000 profit

JABA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JABA AS own?

JABA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JABA AS

Who owns JABA AS?

JANN ROGER BARLAUP-ÅSNES is the largest registered owner, with 100.0%.

What is the revenue of JABA AS?

JABA AS had revenue of NOK 3.2m in 2025.

Who is the general manager of JABA AS?

Jann Roger Barlaup-Åsnes is registered as general manager of JABA AS.

Where is JABA AS based?

JABA AS has its business address in Skien.

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.