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

BRENNE UTLEIE AS

Org. no. 929552202 Limited company (AS) Levanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 239,000
Operating profit NOK 68,000
Equity NOK 462,000
Incorporated 2022
Share capital NOK 300,000

Signals

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

BRENNE UTLEIE AS is registered as a limited company in Levanger, Trøndelag with organisation number 929552202. 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 300,000, divided into 300 shares. The company's stated purpose is: “Investering i fast eiendom for utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 239,000 in revenue and NOK 68,000 in operating profit.

Key figures · 2025

Revenue
NOK 239,000
▲ +14 %
Operating profit
NOK 68,000
▲ +26 %
Equity
NOK 462,000
▲ +13 %
Est. value
NOK 509,000

Financial health · 2025

Liquidity
4.44
Very good
Current assets ÷ current liabilities
Profitability
14.7%
Good
Return on total assets
Solidity
92.7%
Very good
Equity as a share of total capital

Who owns BRENNE UTLEIE AS?

BRENNE UTLEIE AS
NOK 239,000 rev. · NOK 68,000 profit

BRENNE UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRENNE UTLEIE AS

Who owns BRENNE UTLEIE AS?

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

What is the revenue of BRENNE UTLEIE AS?

BRENNE UTLEIE AS had revenue of NOK 239,000 in 2025.

Where is BRENNE UTLEIE AS based?

BRENNE UTLEIE AS has its business address in Skogn.

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.