BIZTRAC BETA
Construction of residential and non-residential buildings

LAFTON BOLIG AS

Org. no. 913359097 Limited company (AS) Ringerike Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK 363,000
Equity NOK 14.2m
Incorporated 2014
Share capital NOK 50,000

Signals

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

LAFTON BOLIG AS is registered as a limited company in Ringerike, Buskerud with organisation number 913359097. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Oppføring og salg av boliger og det som derved er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK 363,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK 363,000
Equity
NOK 14.2m
Est. value
NOK 7.5m

Financial health · 2024

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

Who owns LAFTON BOLIG AS?

LAFTON EIENDOM AS
LAFTON BOLIG AS
NOK 6.0m rev. · NOK 363,000 profit

LAFTON BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAFTON BOLIG AS

Who owns LAFTON BOLIG AS?

LAFTON EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of LAFTON BOLIG AS?

LAFTON BOLIG AS had revenue of NOK 6.0m in 2024.

Who is the general manager of LAFTON BOLIG AS?

Sindre Lafton is registered as general manager of LAFTON BOLIG AS.

Where is LAFTON BOLIG AS based?

LAFTON BOLIG AS has its business address in Hønefoss.

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.