BIZTRAC BETA
Buying and selling of own real estate

SNØTIND-EIENDOM AS

Org. no. 925104205 Limited company (AS) Bodø Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 655,000
Operating profit NOK 548,000
Equity NOK −23,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−23k kr).

SNØTIND-EIENDOM AS is registered as a limited company in Bodø, Nordland with organisation number 925104205. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drifte, vedlikeholde herunder kjøp og salg av eiendom samt utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 655,000 in revenue and NOK 548,000 in operating profit.

Key figures · 2024

Revenue
NOK 655,000
Operating profit
NOK 548,000
Equity
NOK −23,000
Est. value
NOK 3.8m

Financial health · 2024

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SNØTIND-EIENDOM AS?

AKOLBERG HOLDING AS
SNØTIND-EIENDOM AS
NOK 655,000 rev. · NOK 548,000 profit

SNØTIND-EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNØTIND-EIENDOM AS

Who owns SNØTIND-EIENDOM AS?

AKOLBERG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SNØTIND-EIENDOM AS?

SNØTIND-EIENDOM AS had revenue of NOK 655,000 in 2024.

Who is the general manager of SNØTIND-EIENDOM AS?

August Kolberg is registered as general manager of SNØTIND-EIENDOM AS.

Where is SNØTIND-EIENDOM AS based?

SNØTIND-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 15.06.2026.

Report a problem

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