BIZTRAC BETA
COMPANY REGISTER PROFILE
889021802 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 25.08.2026
Rental and operating of own or leased real estate

BOLIG OG NÆRINGSUTLEIE AS

Org. no. 889021802 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −97,000
Equity NOK 9.3m
Incorporated 2005
Share capital NOK 80,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−97k kr).

BOLIG OG NÆRINGSUTLEIE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 889021802. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 80,000, divided into 300 shares. The company's stated purpose is: “Investering i andre selskaper gjennom aksjer, andeler eller på annen måte, samt hva derved står i sammenheng. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”.

Former names: AN-INVEST AS

Key figures · 2025

Operating profit
NOK −97,000
Equity
NOK 9.3m
Est. value
NOK 8.4m

Financial health · 2025

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

Who owns BOLIG OG NÆRINGSUTLEIE AS?

ARVE NORDBOTN
BOLIG OG NÆRINGSUTLEIE AS
· NOK −97,000 profit

BOLIG OG NÆRINGSUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIG OG NÆRINGSUTLEIE AS

Who owns BOLIG OG NÆRINGSUTLEIE AS?

ARVE NORDBOTN is the largest registered owner, with 100.0%.

Who is the general manager of BOLIG OG NÆRINGSUTLEIE AS?

Arve Nordbotn is registered as general manager of BOLIG OG NÆRINGSUTLEIE AS.

Where is BOLIG OG NÆRINGSUTLEIE AS based?

BOLIG OG NÆRINGSUTLEIE 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 25.08.2026.

Report a problem

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