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

ART-BOLIG AS

Org. no. 936306586 Limited company (AS) Sarpsborg Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 18,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

ART-BOLIG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 936306586. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikling, samt kjøp og salg av fast eiendom, samt hva som naturlig hører under.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 18,000
Est. value
NOK 17,000

Financial health · 2025

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

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

Who owns ART-BOLIG AS?

ART-BOLIG AS
NOK 0 rev. · NOK −12,000 profit

ART-BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ART-BOLIG AS

Who owns ART-BOLIG AS?

ART GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of ART-BOLIG AS?

ART-BOLIG AS had revenue of NOK 0 in 2025.

Who is the general manager of ART-BOLIG AS?

Jehona Rukiqi is registered as general manager of ART-BOLIG AS.

Where is ART-BOLIG AS based?

ART-BOLIG AS has its business address in Borgenhaugen.

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.