biztrac. BETA
COMPANY REGISTER PROFILE
934653084 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

JÆRBU NÆRING 2 AS

Org. no. 934653084 Limited company (AS) Time Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 9,000
Incorporated 2024
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-09-28 Adresseendring registrert 2026-09-28.

JÆRBU NÆRING 2 AS is registered as a limited company in Time, Rogaland with organisation number 934653084. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −12,000
▼ −546 %
Equity
NOK 9,000
▼ −52 %
Est. value
NOK 8,000

Financial health · 2025

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

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

Who owns JÆRBU NÆRING 2 AS?

JÆRBU NÆRING 2 AS
· NOK −12,000 profit

JÆRBU NÆRING 2 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JÆRBU NÆRING 2 AS er morselskap for 5 datterselskaper:

Frequently asked questions about JÆRBU NÆRING 2 AS

Who owns JÆRBU NÆRING 2 AS?

ACTIVUM BRYNE AS is the largest registered owner, with 100.0%.

Where is JÆRBU NÆRING 2 AS based?

JÆRBU NÆRING 2 AS has its business address in Bryne.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.