BIZTRAC BETA
Rental and operating of own or leased real estate

FOSS EIENDOM AS

Org. no. 938625573 Limited company (AS) Holmestrand Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 546,000
Equity NOK 5.5m
Incorporated 1986
Share capital NOK 100,000

FOSS EIENDOM AS is registered as a limited company in Holmestrand, Vestfold with organisation number 938625573. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og drive utleie av forretningslokaler og hva dermed står i forbindelse, beslektet eller annen virksomhet samt deltakelse i andre selskaper ved aksjetegning, kjøp av andeler eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 546,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 546,000
Equity
NOK 5.5m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns FOSS EIENDOM AS?

BIRGIT BONDEN HØRTHE
FOSS EIENDOM AS
NOK 2.7m rev. · NOK 546,000 profit

FOSS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOSS EIENDOM AS

Who owns FOSS EIENDOM AS?

BIRGIT BONDEN HØRTHE is the largest registered owner, with 100.0%.

What is the revenue of FOSS EIENDOM AS?

FOSS EIENDOM AS had revenue of NOK 2.7m in 2024.

Who is the general manager of FOSS EIENDOM AS?

Ole Amund Bonden Hørthe is registered as general manager of FOSS EIENDOM AS.

Where is FOSS EIENDOM AS based?

FOSS EIENDOM AS has its business address in Sande I Vestfold.

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.