biztrac. BETA
COMPANY REGISTER PROFILE
989115219 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

IVAR SEIM AS

Org. no. 989115219 Limited company (AS) Sandefjord Incorporated 2005 Active
Revenue 2025 NOK 1.5m
Operating profit NOK −116,000
Equity NOK 5.9m
Incorporated 2005
Share capital NOK 31,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−116k kr).

IVAR SEIM AS is registered as a limited company in Sandefjord, Vestfold with organisation number 989115219. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 31,000, divided into 4400 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom, tomter, maskiner, arbeidskraft og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −116,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +84 %
Operating profit
NOK −116,000
▼ −208 %
Equity
NOK 5.9m
▼ −4 %
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
-1.5%
Not satisfactory
Return on total assets
Solidity
95.4%
Very good
Equity as a share of total capital

Who owns IVAR SEIM AS?

IVAR SEIM AS
NOK 1.5m rev. · NOK −116,000 profit

IVAR SEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IVAR SEIM AS

Who owns IVAR SEIM AS?

Ivar Seim is the largest registered owner, with 100.0%.

What is the revenue of IVAR SEIM AS?

IVAR SEIM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of IVAR SEIM AS?

Ivar Seim is registered as general manager of IVAR SEIM AS.

Where is IVAR SEIM AS based?

IVAR SEIM AS has its business address in Sandefjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.