BIZTRAC BETA
Rental and operating of own or leased real estate

SNIPETORPGATA 13B AS

Org. no. 921588062 Limited company (AS) Skien Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.1m
Equity NOK 31,000
Incorporated 2018
Share capital NOK 30,000

SNIPETORPGATA 13B AS is registered as a limited company in Skien, Telemark with organisation number 921588062. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie av egen fast eiendom”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.1m
Equity
NOK 31,000
Est. value
NOK 1.8m

Financial health · 2024

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.4%
Weak
Equity as a share of total capital

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

Who owns SNIPETORPGATA 13B AS?

LØVSTAD EIENDOM AS
SNIPETORPGATA 13B AS
NOK 1.7m rev. · NOK 1.1m profit

SNIPETORPGATA 13B AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SNIPETORPGATA 13B AS er morselskap for 1 datterselskap:

Frequently asked questions about SNIPETORPGATA 13B AS

Who owns SNIPETORPGATA 13B AS?

LØVSTAD EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SNIPETORPGATA 13B AS?

SNIPETORPGATA 13B AS had revenue of NOK 1.7m in 2024.

Who is the general manager of SNIPETORPGATA 13B AS?

Alexander Emil Løvstad is registered as general manager of SNIPETORPGATA 13B AS.

Where is SNIPETORPGATA 13B AS based?

SNIPETORPGATA 13B AS has its business address in Skien.

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.