BIZTRAC BETA
Rental and operating of own or leased real estate

FOSS STRØMSBORG EIENDOM AS

Org. no. 986972048 Limited company (AS) Enebakk Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 2.7m
Equity NOK 15.9m
Incorporated 2004
Share capital NOK 100,000

FOSS STRØMSBORG EIENDOM AS is registered as a limited company in Enebakk, Akershus with organisation number 986972048. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte fast eiendom og andre formuesverdier, samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 2.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 2.7m
Equity
NOK 15.9m
Est. value
NOK 16.1m

Financial health · 2024

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

Who owns FOSS STRØMSBORG EIENDOM AS?

ENEBAKK HOLDING AS
FOSS STRØMSBORG EIENDOM AS
NOK 3.5m rev. · NOK 2.7m profit

FOSS STRØMSBORG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOSS STRØMSBORG EIENDOM AS

Who owns FOSS STRØMSBORG EIENDOM AS?

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

What is the revenue of FOSS STRØMSBORG EIENDOM AS?

FOSS STRØMSBORG EIENDOM AS had revenue of NOK 3.5m in 2024.

Who is the general manager of FOSS STRØMSBORG EIENDOM AS?

Stian Olav Karlsen is registered as general manager of FOSS STRØMSBORG EIENDOM AS.

Where is FOSS STRØMSBORG EIENDOM AS based?

FOSS STRØMSBORG EIENDOM AS has its business address in Ytre Enebakk.

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.