BIZTRAC BETA
Rental and operating of own or leased real estate

LOGENE I NAMSOS AS

Org. no. 989574442 Limited company (AS) Namsos Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 808,000
Operating profit NOK 191,000
Equity NOK 1.3m
Incorporated 2006
Share capital NOK 1.0m

LOGENE I NAMSOS AS is registered as a limited company in Namsos, Trøndelag with organisation number 989574442. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Å eie og drive seksjon 2 i Sparebankbygg Namsos. Seksjonen skal tjene som felles logelokaler for Frimurerlogene og Odd fellow-logene i Namsos. Selskapet skal ikke ha overskudd til formål. Ved oppløsning skal formue og eventuelt overskudd fordeles til aksjonærene etter det antall aksjer aksjonæren eier.”. The most recent filed accounts, for the 2024 financial year, show NOK 808,000 in revenue and NOK 191,000 in operating profit.

Key figures · 2024

Revenue
NOK 808,000
Operating profit
NOK 191,000
Equity
NOK 1.3m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns LOGENE I NAMSOS AS?

ST JOHANNES LOGEN CAPELLA
LOGENE I NAMSOS AS
NOK 808,000 rev. · NOK 191,000 profit

LOGENE I NAMSOS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOGENE I NAMSOS AS

Who owns LOGENE I NAMSOS AS?

ST JOHANNES LOGEN CAPELLA is the largest registered owner, with 50.0%.

What is the revenue of LOGENE I NAMSOS AS?

LOGENE I NAMSOS AS had revenue of NOK 808,000 in 2024.

Where is LOGENE I NAMSOS AS based?

LOGENE I NAMSOS 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.