BIZTRAC BETA
Rental and operating of own or leased real estate

SEBO UTLEIE AS

Org. no. 930100285 Limited company (AS) Levanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 406,000
Operating profit NOK 114,000
Equity NOK −370,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−370k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SEBO UTLEIE AS is registered as a limited company in Levanger, Trøndelag with organisation number 930100285. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie, kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 406,000 in revenue and NOK 114,000 in operating profit.

Key figures · 2025

Revenue
NOK 406,000
Operating profit
NOK 114,000
Equity
NOK −370,000
Est. value
NOK 780,000

Financial health · 2025

Liquidity
51.00
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SEBO UTLEIE AS?

SEBO BOLIGER AS
SEBO UTLEIE AS
NOK 406,000 rev. · NOK 114,000 profit

SEBO UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEBO UTLEIE AS

Who owns SEBO UTLEIE AS?

SEBO BOLIGER AS is the largest registered owner, with 90.0%.

What is the revenue of SEBO UTLEIE AS?

SEBO UTLEIE AS had revenue of NOK 406,000 in 2025.

Where is SEBO UTLEIE AS based?

SEBO UTLEIE AS has its business address in Levanger.

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.