BIZTRAC BETA
COMPANY REGISTER PROFILE
930121142 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

JACK AS

Org. no. 930121142 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 142,000
Equity NOK 88,000
Incorporated 2022
Share capital NOK 30,000

JACK AS is registered as a limited company in Oslo, Oslo with organisation number 930121142. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Vaktmestertjenester, rehabilitering av bygg, herunder trearbeider, gulvlegging, fliser og alt som er forbundet med dette. Investering og utvikling av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 142,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 142,000
Equity
NOK 88,000
Est. value
NOK 452,000

Financial health · 2025

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

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

Who owns JACK AS?

JACEK PAWEL LABORDA
JACK AS
NOK 1.2m rev. · NOK 142,000 profit

JACK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JACK AS

Who owns JACK AS?

JACEK PAWEL LABORDA is the largest registered owner, with 100.0%.

What is the revenue of JACK AS?

JACK AS had revenue of NOK 1.2m in 2025.

Who is the general manager of JACK AS?

Jacek Pawel Laborda is registered as general manager of JACK AS.

Where is JACK AS based?

JACK 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.