BIZTRAC BETA
Plant propagation

SEIERSTAD BYGG OG ANLEGG AS

Org. no. 945193565 Limited company (AS) Aurskog-Høland Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 306,000
Operating profit NOK 8,000
Equity NOK 426,000
Incorporated 1987
Share capital NOK 100,000

SEIERSTAD BYGG OG ANLEGG AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 945193565. The business is classified under plant propagation (NACE 01.300). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av plener, torvtak, vedlikehold av anlegg og andre produkter/tjenster som naturlig hører sammen med dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 306,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 306,000
Operating profit
NOK 8,000
Equity
NOK 426,000
Est. value
NOK 239,000

Financial health · 2024

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

Who owns SEIERSTAD BYGG OG ANLEGG AS?

CHRISTEN SEIERSTAD
SEIERSTAD BYGG OG ANLEGG AS
NOK 306,000 rev. · NOK 8,000 profit

SEIERSTAD BYGG OG ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEIERSTAD BYGG OG ANLEGG AS

Who owns SEIERSTAD BYGG OG ANLEGG AS?

CHRISTEN SEIERSTAD is the largest registered owner, with 100.0%.

What is the revenue of SEIERSTAD BYGG OG ANLEGG AS?

SEIERSTAD BYGG OG ANLEGG AS had revenue of NOK 306,000 in 2024.

Who is the general manager of SEIERSTAD BYGG OG ANLEGG AS?

Christen Seierstad is registered as general manager of SEIERSTAD BYGG OG ANLEGG AS.

Where is SEIERSTAD BYGG OG ANLEGG AS based?

SEIERSTAD BYGG OG ANLEGG AS has its business address in Løken.

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.