BIZTRAC BETA
COMPANY REGISTER PROFILE
933832228 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

SNEKKER BYGG AS

Org. no. 933832228 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 73,000
Operating profit NOK 60,000
Equity NOK 72,000
Incorporated 2024
Share capital NOK 30,000

SNEKKER BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 933832228. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggmestertjenester, konsulenttjenester, kjøp og salg av fast eiendom, prosjektutvikling og annet som står i denne forbindelse, herunder delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 73,000 in revenue and NOK 60,000 in operating profit.

Key figures · 2025

Revenue
NOK 73,000
Operating profit
NOK 60,000
Equity
NOK 72,000
Est. value
NOK 218,000

Financial health · 2025

Liquidity
5.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
81.3%
Weak
Equity as a share of total capital

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

Who owns SNEKKER BYGG AS?

PAAL STIAN AAGENÆS
SNEKKER BYGG AS
NOK 73,000 rev. · NOK 60,000 profit

SNEKKER BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNEKKER BYGG AS

Who owns SNEKKER BYGG AS?

PAAL STIAN AAGENÆS is the largest registered owner, with 100.0%.

What is the revenue of SNEKKER BYGG AS?

SNEKKER BYGG AS had revenue of NOK 73,000 in 2025.

Where is SNEKKER BYGG AS based?

SNEKKER BYGG AS has its business address in Oslo.

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.