BIZTRAC BETA
Rental and operating of own or leased real estate

SNEKKERKOMPANIET EIENDOM AS

Org. no. 912814807 Limited company (AS) Tønsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 769,000
Operating profit NOK 195,000
Equity NOK 2.2m
Incorporated 2013
Share capital NOK 125,000

SNEKKERKOMPANIET EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 912814807. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 125,000, divided into 10000 shares. The company's stated purpose is: “Eie fast eiendom, aksjer i andre selskaper og dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 769,000 in revenue and NOK 195,000 in operating profit.

Key figures · 2024

Revenue
NOK 769,000
Operating profit
NOK 195,000
Equity
NOK 2.2m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns SNEKKERKOMPANIET EIENDOM AS?

ROAR BECKER
SNEKKERKOMPANIET EIENDOM AS
NOK 769,000 rev. · NOK 195,000 profit

SNEKKERKOMPANIET EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SNEKKERKOMPANIET EIENDOM AS

Who owns SNEKKERKOMPANIET EIENDOM AS?

ROAR BECKER is the largest registered owner, with 20.0%.

What is the revenue of SNEKKERKOMPANIET EIENDOM AS?

SNEKKERKOMPANIET EIENDOM AS had revenue of NOK 769,000 in 2024.

Who is the general manager of SNEKKERKOMPANIET EIENDOM AS?

Jon Andreas Lager is registered as general manager of SNEKKERKOMPANIET EIENDOM AS.

Where is SNEKKERKOMPANIET EIENDOM AS based?

SNEKKERKOMPANIET EIENDOM AS has its business address in Barkåker.

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.