BIZTRAC BETA
Rental and operating of own or leased real estate

NÆRBYEN UTLEIEBOLIG AS

Org. no. 921284225 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 5.3m
Equity NOK 18.2m
Incorporated 2018
Share capital NOK 78,000

Signals

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

NÆRBYEN UTLEIEBOLIG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921284225. 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 78,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom samt hva hermed står i forbindelse, herunder deltakelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 5.3m in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 5.3m
Equity
NOK 18.2m
Est. value
NOK 23.6m

Financial health · 2025

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

Who owns NÆRBYEN UTLEIEBOLIG AS?

FROST HOLDING AS
NÆRBYEN UTLEIEBOLIG AS
NOK 5.6m rev. · NOK 5.3m profit

NÆRBYEN UTLEIEBOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NÆRBYEN UTLEIEBOLIG AS

Who owns NÆRBYEN UTLEIEBOLIG AS?

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

What is the revenue of NÆRBYEN UTLEIEBOLIG AS?

NÆRBYEN UTLEIEBOLIG AS had revenue of NOK 5.6m in 2025.

Where is NÆRBYEN UTLEIEBOLIG AS based?

NÆRBYEN UTLEIEBOLIG AS has its business address in Trondheim.

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.