BIZTRAC BETA
Construction of residential and non-residential buildings

FLIKKERUD BYGGTJENESTER AS

Org. no. 922215863 Limited company (AS) Nord-Odal Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 101,000
Equity NOK 96,000
Incorporated 2019
Share capital NOK 30,000

FLIKKERUD BYGGTJENESTER AS is registered as a limited company in Nord-Odal, Innlandet with organisation number 922215863. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Håndverktjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 101,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 101,000
Equity
NOK 96,000
Est. value
NOK 383,000

Financial health · 2024

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

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

Who owns FLIKKERUD BYGGTJENESTER AS?

LASSE FLIKKERUD
FLIKKERUD BYGGTJENESTER AS
NOK 2.2m rev. · NOK 101,000 profit

FLIKKERUD BYGGTJENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLIKKERUD BYGGTJENESTER AS

Who owns FLIKKERUD BYGGTJENESTER AS?

LASSE FLIKKERUD is the largest registered owner, with 50.0%.

What is the revenue of FLIKKERUD BYGGTJENESTER AS?

FLIKKERUD BYGGTJENESTER AS had revenue of NOK 2.2m in 2024.

Who is the general manager of FLIKKERUD BYGGTJENESTER AS?

Lasse Flikkerud is registered as general manager of FLIKKERUD BYGGTJENESTER AS.

Where is FLIKKERUD BYGGTJENESTER AS based?

FLIKKERUD BYGGTJENESTER AS has its business address in Knapper.

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.