BIZTRAC BETA
Rental and operating of own or leased real estate

FOSBY PETICO EIENDOM AS

Org. no. 997160193 Limited company (AS) Sarpsborg Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 11.1m
Operating profit NOK 3.1m
Equity NOK 5.0m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FOSBY PETICO EIENDOM AS is registered as a limited company in Sarpsborg, Østfold with organisation number 997160193. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Erverve, forvalte og selge aksjer, andeler og faste eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.1m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 11.1m
Operating profit
NOK 3.1m
Equity
NOK 5.0m
Est. value
NOK 8.0m

Financial health · 2024

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

Who owns FOSBY PETICO EIENDOM AS?

FOSBY AS
FOSBY PETICO EIENDOM AS
NOK 11.1m rev. · NOK 3.1m profit

FOSBY PETICO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FOSBY PETICO EIENDOM AS er morselskap for 5 datterselskaper:

Frequently asked questions about FOSBY PETICO EIENDOM AS

Who owns FOSBY PETICO EIENDOM AS?

FOSBY AS is the largest registered owner, with 100.0%.

What is the revenue of FOSBY PETICO EIENDOM AS?

FOSBY PETICO EIENDOM AS had revenue of NOK 11.1m in 2024.

Where is FOSBY PETICO EIENDOM AS based?

FOSBY PETICO EIENDOM AS has its business address in Sarpsborg.

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.