biztrac. BETA
COMPANY REGISTER PROFILE
997791711 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

SALTEN EIENDOM AS

Org. no. 997791711 Limited company (AS) Bodø Incorporated 2012 Active
Revenue 2025 NOK 1.5m
Operating profit NOK 319,000
Equity NOK 5.0m
Incorporated 2012
Share capital NOK 100,000

SALTEN EIENDOM AS is registered as a limited company in Bodø, Nordland with organisation number 997791711. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapet skal drive forvaltning og utvikling av eiendom, investeinger i aksjer og andeler, samt hva som her står i naturlig frobindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 319,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▼ −57 %
Operating profit
NOK 319,000
▼ −85 %
Equity
NOK 5.0m
▲ +4 %
Est. value
NOK 4.6m

Financial health · 2025

Liquidity
3.29
Very good
Current assets ÷ current liabilities
Profitability
5.4%
Weak
Return on total assets
Solidity
45.4%
Very good
Equity as a share of total capital

Who owns SALTEN EIENDOM AS?

SALTEN EIENDOM AS
NOK 1.5m rev. · NOK 319,000 profit

SALTEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SALTEN EIENDOM AS

Who owns SALTEN EIENDOM AS?

Trond Nilsskog is the largest registered owner, with 50.0%.

What is the revenue of SALTEN EIENDOM AS?

SALTEN EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of SALTEN EIENDOM AS?

Trond Nilsskog is registered as general manager of SALTEN EIENDOM AS.

Where is SALTEN EIENDOM AS based?

SALTEN EIENDOM AS has its business address in Bodø.

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.