BIZTRAC BETA
Development of building projects

JELLESTADVEIEN 33 AS

Org. no. 935909899 Limited company (AS) Sarpsborg Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 305,000
Operating profit NOK 138,000
Equity NOK 33,000
Incorporated 2025
Share capital NOK 30,000

JELLESTADVEIEN 33 AS is registered as a limited company in Sarpsborg, Østfold with organisation number 935909899. 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 3000 shares. The company's stated purpose is: “Kjøp, utvikling og utleie av fast eiendom, inkludert, men ikke begrenset til, utleie av næringseiendom, kontorer, lagerplass, kommersielle eiendommer og andre typer fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 305,000 in revenue and NOK 138,000 in operating profit.

Key figures · 2025

Revenue
NOK 305,000
Operating profit
NOK 138,000
Equity
NOK 33,000
Est. value
NOK 288,000

Financial health · 2025

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

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

Who owns JELLESTADVEIEN 33 AS?

JWJ HOLDING AS
JELLESTADVEIEN 33 AS
NOK 305,000 rev. · NOK 138,000 profit

JELLESTADVEIEN 33 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JELLESTADVEIEN 33 AS er morselskap for 1 datterselskap:

Frequently asked questions about JELLESTADVEIEN 33 AS

Who owns JELLESTADVEIEN 33 AS?

JWJ HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JELLESTADVEIEN 33 AS?

JELLESTADVEIEN 33 AS had revenue of NOK 305,000 in 2025.

Where is JELLESTADVEIEN 33 AS based?

JELLESTADVEIEN 33 AS has its business address in Hafslundsøy.

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.