BIZTRAC BETA
Rental and operating of own or leased real estate

SEA ECO EIENDOM AS

Org. no. 829712962 Limited company (AS) Harstad Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 620,000
Operating profit NOK 63,000
Equity NOK −1.5m
Incorporated 2022
Share capital NOK 30,000

Signals

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

SEA ECO EIENDOM AS is registered as a limited company in Harstad, Troms with organisation number 829712962. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 620,000 in revenue and NOK 63,000 in operating profit.

Key figures · 2024

Revenue
NOK 620,000
Operating profit
NOK 63,000
Equity
NOK −1.5m
Est. value
NOK 432,000

Financial health · 2024

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-15.4%
Weak
Equity as a share of total capital

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

Who owns SEA ECO EIENDOM AS?

GHOLAM REZA AHMADI
SEA ECO EIENDOM AS
NOK 620,000 rev. · NOK 63,000 profit

SEA ECO EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEA ECO EIENDOM AS

Who owns SEA ECO EIENDOM AS?

GHOLAM REZA AHMADI is the largest registered owner, with 40.0%.

What is the revenue of SEA ECO EIENDOM AS?

SEA ECO EIENDOM AS had revenue of NOK 620,000 in 2024.

Who is the general manager of SEA ECO EIENDOM AS?

Tone Rasmussen is registered as general manager of SEA ECO EIENDOM AS.

Where is SEA ECO EIENDOM AS based?

SEA ECO EIENDOM AS has its business address in Harstad.

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.