biztrac. BETA
COMPANY REGISTER PROFILE
993726451 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE

Org. no. 993726451 Condominium flat owner (ESEK) Fredrikstad Incorporated 2006 Active
Revenue 2025 NOK 1.1m
Operating profit NOK 294,000
Equity NOK −1.4m
Incorporated 2006

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,4 mill kr).

OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE is registered as a condominium flat owner in Fredrikstad, Østfold with organisation number 993726451. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2006. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 294,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +8 %
Operating profit
NOK 294,000
▲ +185 %
Equity
NOK −1.4m
▲ +13 %

Financial health · 2025

Liquidity
15.98
Very good
Current assets ÷ current liabilities
Profitability
44.5%
Very good
Return on total assets
Solidity
-206.3%
Weak
Equity as a share of total capital

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

Who owns OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE?

No shareholders are registered for OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE

What is the revenue of OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE?

OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE had revenue of NOK 1.1m in 2025.

Where is OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE based?

OSKARSGT. 64/PELLYGT.63/ JERNBANEGT. 10 SAMEIE has its business address in Kråkerøy.

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.