BIZTRAC BETA
Rental and operating of own or leased real estate

CEB UTVIKLING 1 AS

Org. no. 935490979 Limited company (AS) Løten Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 1.0m
Incorporated 2025
Share capital NOK 81,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-19 Adresseendring registrert 2026-06-19.

CEB UTVIKLING 1 AS is registered as a limited company in Løten, Innlandet with organisation number 935490979. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 81,000, divided into 500 shares. The company's stated purpose is: “Å eie og utvikle fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 1.0m
Est. value
NOK 953,000

Financial health · 2025

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

Who owns CEB UTVIKLING 1 AS?

T.L EIENDOM OG INVEST AS
CEB UTVIKLING 1 AS
NOK 0 rev. · NOK −2,000 profit

CEB UTVIKLING 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CEB UTVIKLING 1 AS

Who owns CEB UTVIKLING 1 AS?

T.L EIENDOM OG INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of CEB UTVIKLING 1 AS?

CEB UTVIKLING 1 AS had revenue of NOK 0 in 2025.

Where is CEB UTVIKLING 1 AS based?

CEB UTVIKLING 1 AS has its business address in Ådalsbruk.

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.