biztrac. BETA
COMPANY REGISTER PROFILE
932265338 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ØSTFOLD OFFENTLIG BYGG AS

Org. no. 932265338 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −213,000
Equity NOK 45.1m
Incorporated 2023
Share capital NOK 70,000

Signals

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

ØSTFOLD OFFENTLIG BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 932265338. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 70,000, divided into 1000 shares. The company's stated purpose is: “Utvikling, forvaltning og investering i andre selskaper, samt investering i fast eiendom og andre formuesgoder og alt som står i forbindelse med de forannevnte virksomheter.”.

Former names: NJORD PROSJEKT 104 AS

Key figures · 2025

Operating profit
NOK −213,000
▼ −1923 %
Equity
NOK 45.1m
▲ +241036 %
Est. value
NOK 41.1m

Financial health · 2025

Liquidity
1.98
Good
Current assets ÷ current liabilities
Profitability
3.1%
Weak
Return on total assets
Solidity
42.2%
Very good
Equity as a share of total capital

Who owns ØSTFOLD OFFENTLIG BYGG AS?

ØSTFOLD OFFENTLIG BYGG AS
· NOK −213,000 profit

ØSTFOLD OFFENTLIG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØSTFOLD OFFENTLIG BYGG AS own?

ØSTFOLD OFFENTLIG BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØSTFOLD OFFENTLIG BYGG AS

Who owns ØSTFOLD OFFENTLIG BYGG AS?

NJORD PUBLIC PROPERTY II AS is the largest registered owner, with 100.0%.

Where is ØSTFOLD OFFENTLIG BYGG AS based?

ØSTFOLD OFFENTLIG BYGG 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 03.10.2026.

Report a problem

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