BIZTRAC BETA
Retail sale of footwear and leather goods

SNOS LAGUNEN AS

Org. no. 929916263 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 10.0m
Operating profit NOK 1.7m
Equity NOK 690,000
Incorporated 2022
Employees 8
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SNOS LAGUNEN AS is registered as a limited company in Bergen, Vestland with organisation number 929916263. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Butikkhandel med reiseeffekter av lær og lærimitasjoner og varer av lær.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 10.0m
Operating profit
NOK 1.7m
Equity
NOK 690,000
Est. value
NOK 5.6m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.3%
Good
Equity as a share of total capital

Who owns SNOS LAGUNEN AS?

SN OS HOLDING AS
SNOS LAGUNEN AS
NOK 10.0m rev. · NOK 1.7m profit

SNOS LAGUNEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNOS LAGUNEN AS

Who owns SNOS LAGUNEN AS?

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

What is the revenue of SNOS LAGUNEN AS?

SNOS LAGUNEN AS had revenue of NOK 10.0m in 2025.

Who is the general manager of SNOS LAGUNEN AS?

Ole Sverre Mengkrog is registered as general manager of SNOS LAGUNEN AS.

Where is SNOS LAGUNEN AS based?

SNOS LAGUNEN AS has its business address in Rådal.

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.