biztrac. BETA
COMPANY REGISTER PROFILE
934988396 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

SNEKKER-LARSEN AS

Org. no. 934988396 Limited company (AS) Bergen Incorporated 2025 Active
Revenue 2025 NOK 1.8m
Operating profit NOK 26,000
Equity NOK 29,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-09-21 Adresseendring registrert 2026-09-21.

SNEKKER-LARSEN AS is registered as a limited company in Bergen, Vestland with organisation number 934988396. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Snekkerarbeid, servicearbeid og kundetilpasset snekkerarbeid og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 26,000
Equity
NOK 29,000
Est. value
NOK 72,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
6.8%
Weak
Equity as a share of total capital

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

Who owns SNEKKER-LARSEN AS?

SNEKKER-LARSEN AS
NOK 1.8m rev. · NOK 26,000 profit

SNEKKER-LARSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNEKKER-LARSEN AS

Who owns SNEKKER-LARSEN AS?

Trond Arild Klever is the largest registered owner, with 100.0%.

What is the revenue of SNEKKER-LARSEN AS?

SNEKKER-LARSEN AS had revenue of NOK 1.8m in 2025.

Where is SNEKKER-LARSEN AS based?

SNEKKER-LARSEN 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 03.10.2026.

Report a problem

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