BIZTRAC BETA
Rental and operating of own or leased real estate

SETH AS

Org. no. 922285284 Limited company (AS) Bærum Incorporated 1978 Active
Ownership graph ↗
Revenue 2024 NOK 891,000
Operating profit NOK −156,000
Equity NOK 8.5m
Incorporated 1978
Share capital NOK 900,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−156k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SETH AS is registered as a limited company in Bærum, Akershus with organisation number 922285284. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1978. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Kjøp, salg, drift og utleie av fast eiendom samt investering i andre objekt, herunder aksjer og virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 891,000 in revenue and NOK −156,000 in operating profit.

Key figures · 2024

Revenue
NOK 891,000
Operating profit
NOK −156,000
Equity
NOK 8.5m
Est. value
NOK 7.1m

Financial health · 2024

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

Who owns SETH AS?

MONS HOLDING AS
SETH AS
NOK 891,000 rev. · NOK −156,000 profit

SETH AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SETH AS er morselskap for 2 datterselskaper:

Frequently asked questions about SETH AS

Who owns SETH AS?

MONS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SETH AS?

SETH AS had revenue of NOK 891,000 in 2024.

Where is SETH AS based?

SETH AS has its business address in Snarøya.

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.