BIZTRAC BETA
Construction of residential and non-residential buildings

SEABIRD EIENDOM AS

Org. no. 997342046 Limited company (AS) Bodø Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 3.9m
Equity NOK 878,000
Incorporated 2011
Share capital NOK 1.3m

Signals

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

SEABIRD EIENDOM AS is registered as a limited company in Bodø, Nordland with organisation number 997342046. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 1.3m, divided into 190623 shares. The company's stated purpose is: “Utvikle, forvalte og eie av fast eiendom samt annen virksomhet som står i sammenheng med dette, herunder også deltakelse i andre selskaper med liknende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 3.9m in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 3.9m
Equity
NOK 878,000
Est. value
NOK 9.1m

Financial health · 2024

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

Who owns SEABIRD EIENDOM AS?

NYE 5 OLSEN HOLDING AS
SEABIRD EIENDOM AS
NOK 8.2m rev. · NOK 3.9m profit

SEABIRD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEABIRD EIENDOM AS

Who owns SEABIRD EIENDOM AS?

NYE 5 OLSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SEABIRD EIENDOM AS?

SEABIRD EIENDOM AS had revenue of NOK 8.2m in 2024.

Where is SEABIRD EIENDOM AS based?

SEABIRD EIENDOM AS has its business address in Bodø.

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.