BIZTRAC BETA
Development of building projects

EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS

Org. no. 915743323 Limited company (AS) Færder Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 910,000
Operating profit NOK 296,000
Equity NOK 941,000
Incorporated 2015
Share capital NOK 90,000

EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS is registered as a limited company in Færder, Vestfold with organisation number 915743323. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 90,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utvikling av eiendom. Samt delta som aksjonær, andelshaver eller på annen måte i selskaper med økonomiske formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 910,000 in revenue and NOK 296,000 in operating profit.

Key figures · 2025

Revenue
NOK 910,000
Operating profit
NOK 296,000
Equity
NOK 941,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS?

TJØME INVEST AS
EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS
NOK 910,000 rev. · NOK 296,000 profit

EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS

Who owns EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS?

TJØME INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS?

EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS had revenue of NOK 910,000 in 2025.

Where is EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS based?

EIENDOMSSELSKAPET LØKKEÅSVEIEN 22B AS has its business address in Skallestad.

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.