BIZTRAC BETA
Intermediation service activities for real estate activities

SALTEN EIENDOMSMEGLING AS

Org. no. 992408065 Limited company (AS) Bodø Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 517,000
Equity NOK 1.3m
Incorporated 2008
Share capital NOK 330,000

SALTEN EIENDOMSMEGLING AS is registered as a limited company in Bodø, Nordland with organisation number 992408065. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2008. Registered share capital is NOK 330,000, divided into 330 shares. The company's stated purpose is: “Eiendomsmegling samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 517,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 517,000
Equity
NOK 1.3m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns SALTEN EIENDOMSMEGLING AS?

ASBJØRN EDVIN INGEBRIGTSEN
SALTEN EIENDOMSMEGLING AS
NOK 3.5m rev. · NOK 517,000 profit

SALTEN EIENDOMSMEGLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALTEN EIENDOMSMEGLING AS

Who owns SALTEN EIENDOMSMEGLING AS?

ASBJØRN EDVIN INGEBRIGTSEN is the largest registered owner, with 100.0%.

What is the revenue of SALTEN EIENDOMSMEGLING AS?

SALTEN EIENDOMSMEGLING AS had revenue of NOK 3.5m in 2025.

Who is the general manager of SALTEN EIENDOMSMEGLING AS?

Asbjørn Edvin Ingebrigtsen is registered as general manager of SALTEN EIENDOMSMEGLING AS.

Where is SALTEN EIENDOMSMEGLING AS based?

SALTEN EIENDOMSMEGLING AS has its business address in Tverlandet.

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.