BIZTRAC BETA
Intermediation service activities for real estate activities

NAMSOS EIENDOMSMEGLING AS

Org. no. 931648667 Limited company (AS) Namsos Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 622,000
Equity NOK 746,000
Incorporated 2023
Share capital NOK 400,000

NAMSOS EIENDOMSMEGLING AS is registered as a limited company in Namsos, Trøndelag with organisation number 931648667. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2023. Registered share capital is NOK 400,000, divided into 400000 shares. The company's stated purpose is: “Drive med eiendomsmegling samt andre aktiviteter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 622,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 622,000
Equity
NOK 746,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.4%
Good
Equity as a share of total capital

Who owns NAMSOS EIENDOMSMEGLING AS?

ELIN BRØNDBO
NAMSOS EIENDOMSMEGLING AS
NOK 3.0m rev. · NOK 622,000 profit

NAMSOS EIENDOMSMEGLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NAMSOS EIENDOMSMEGLING AS

Who owns NAMSOS EIENDOMSMEGLING AS?

ELIN BRØNDBO is the largest registered owner, with 100.0%.

What is the revenue of NAMSOS EIENDOMSMEGLING AS?

NAMSOS EIENDOMSMEGLING AS had revenue of NOK 3.0m in 2024.

Who is the general manager of NAMSOS EIENDOMSMEGLING AS?

Elin Brøndbo is registered as general manager of NAMSOS EIENDOMSMEGLING AS.

Where is NAMSOS EIENDOMSMEGLING AS based?

NAMSOS EIENDOMSMEGLING AS has its business address in Namsos.

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.