BIZTRAC BETA
Joinery installation

OSLO SNEKKER AS

Org. no. 918089462 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 25.2m
Operating profit NOK 797,000
Equity NOK 1.3m
Incorporated 2016
Employees 41
Share capital NOK 100,000

Signals

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

OSLO SNEKKER AS is registered as a limited company in Oslo, Oslo with organisation number 918089462. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2016 and has 41 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Snekring, tømring, montering av dører, vinduer, isolasjon og alt som hva derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.2m in revenue and NOK 797,000 in operating profit.

Key figures · 2024

Revenue
NOK 25.2m
Operating profit
NOK 797,000
Equity
NOK 1.3m
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.9%
Good
Equity as a share of total capital

Who owns OSLO SNEKKER AS?

BJORLAND INVEST AS
OSLO SNEKKER AS
NOK 25.2m rev. · NOK 797,000 profit

OSLO SNEKKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO SNEKKER AS

Who owns OSLO SNEKKER AS?

BJORLAND INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO SNEKKER AS?

OSLO SNEKKER AS had revenue of NOK 25.2m in 2024.

Who is the general manager of OSLO SNEKKER AS?

Christoffer Engebretsen Bjørland is registered as general manager of OSLO SNEKKER AS.

Where is OSLO SNEKKER AS based?

OSLO SNEKKER 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.