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

SEMSVEIEN 40 AS

Org. no. 920318525 Limited company (AS) Lier Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 681,000
Operating profit NOK 106,000
Equity NOK 614,000
Incorporated 2018
Share capital NOK 1.6m

Signals

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

SEMSVEIEN 40 AS is registered as a limited company in Lier, Buskerud with organisation number 920318525. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 1.6m, divided into 1610 shares. The company's stated purpose is: “Kjøp, salg, utleie og drift av fast eiendom samt alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 681,000 in revenue and NOK 106,000 in operating profit.

Key figures · 2025

Revenue
NOK 681,000
▼ −5 %
Operating profit
NOK 106,000
▼ −15 %
Equity
NOK 614,000
▼ −37 %
Est. value
NOK 740,000

Financial health · 2025

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
1.4%
Weak
Return on total assets
Solidity
8.4%
Weak
Equity as a share of total capital

Who owns SEMSVEIEN 40 AS?

SEMSVEIEN 40 AS
NOK 681,000 rev. · NOK 106,000 profit

SEMSVEIEN 40 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEMSVEIEN 40 AS

Who owns SEMSVEIEN 40 AS?

INVESTORIA AS is the largest registered owner, with 100.0%.

What is the revenue of SEMSVEIEN 40 AS?

SEMSVEIEN 40 AS had revenue of NOK 681,000 in 2025.

Where is SEMSVEIEN 40 AS based?

SEMSVEIEN 40 AS has its business address in Lier.

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.