BIZTRAC BETA
COMPANY REGISTER PROFILE
925657905 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

SLITU 1 AS

Org. no. 925657905 Limited company (AS) Aurskog-Høland Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 270,000
Equity NOK 179,000
Incorporated 2020
Share capital NOK 40,000

Signals

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

SLITU 1 AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 925657905. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 270,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +4 %
Operating profit
NOK 270,000
▼ −56 %
Equity
NOK 179,000
▼ −16 %
Est. value
NOK 733,000

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
3.5%
Weak
Return on total assets
Solidity
2.3%
Not satisfactory
Equity as a share of total capital

Who owns SLITU 1 AS?

SLITU 1 AS
NOK 1.1m rev. · NOK 270,000 profit

SLITU 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLITU 1 AS

Who owns SLITU 1 AS?

LITZHEIM BYGG OG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SLITU 1 AS?

SLITU 1 AS had revenue of NOK 1.1m in 2025.

Where is SLITU 1 AS based?

SLITU 1 AS has its business address in Bjørkelangen.

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

Report a problem

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