BIZTRAC BETA
Masonry and bricklaying activities

BYGG OG NATURSTEIN AS

Org. no. 918756051 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 24.5m
Operating profit NOK 4.3m
Equity NOK 62,000
Incorporated 2017
Employees 12
Share capital NOK 30,000

BYGG OG NATURSTEIN AS is registered as a limited company in Drammen, Buskerud with organisation number 918756051. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2017 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tømmer- og steinarbeid, samt produkter og tjenester som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.5m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 24.5m
Operating profit
NOK 4.3m
Equity
NOK 62,000
Est. value
NOK 11.6m

Financial health · 2024

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

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

Who owns BYGG OG NATURSTEIN AS?

LUKERN AS
BYGG OG NATURSTEIN AS
NOK 24.5m rev. · NOK 4.3m profit

BYGG OG NATURSTEIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGG OG NATURSTEIN AS

Who owns BYGG OG NATURSTEIN AS?

LUKERN AS is the largest registered owner, with 100.0%.

What is the revenue of BYGG OG NATURSTEIN AS?

BYGG OG NATURSTEIN AS had revenue of NOK 24.5m in 2024.

Who is the general manager of BYGG OG NATURSTEIN AS?

Lars Fredrik Olsen is registered as general manager of BYGG OG NATURSTEIN AS.

Where is BYGG OG NATURSTEIN AS based?

BYGG OG NATURSTEIN AS has its business address in Krokstadelva.

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.