BIZTRAC BETA
Repair and maintenance of civilian ships and boats

ØSTERÅ EIENDOM AS

Org. no. 989582763 Limited company (AS) Tvedestrand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 959,000
Equity NOK 6.7m
Incorporated 2005
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.

ØSTERÅ EIENDOM AS is registered as a limited company in Tvedestrand, Agder with organisation number 989582763. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eiendomsdrift og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 959,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 959,000
Equity
NOK 6.7m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns ØSTERÅ EIENDOM AS?

SANDØY HOLDING AS
ØSTERÅ EIENDOM AS
NOK 2.5m rev. · NOK 959,000 profit

ØSTERÅ EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØSTERÅ EIENDOM AS

Who owns ØSTERÅ EIENDOM AS?

SANDØY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ØSTERÅ EIENDOM AS?

ØSTERÅ EIENDOM AS had revenue of NOK 2.5m in 2025.

Who is the general manager of ØSTERÅ EIENDOM AS?

Jarle Kristoffersen is registered as general manager of ØSTERÅ EIENDOM AS.

Where is ØSTERÅ EIENDOM AS based?

ØSTERÅ EIENDOM AS has its business address in Tvedestrand.

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.