BIZTRAC BETA
Other personal service activities n.e.c.

LUKRA VEILEDNING AS

Org. no. 927992442 Limited company (AS) Indre Østfold Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 905,000
Operating profit NOK −36,000
Equity NOK 40,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−36k kr).

LUKRA VEILEDNING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 927992442. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Veiledningstjeneste.”. The most recent filed accounts, for the 2024 financial year, show NOK 905,000 in revenue and NOK −36,000 in operating profit.

Key figures · 2024

Revenue
NOK 905,000
Operating profit
NOK −36,000
Equity
NOK 40,000
Est. value
NOK 595,000

Financial health · 2024

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

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

Who owns LUKRA VEILEDNING AS?

LUKRA HOLDING AS
LUKRA VEILEDNING AS
NOK 905,000 rev. · NOK −36,000 profit

LUKRA VEILEDNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUKRA VEILEDNING AS

Who owns LUKRA VEILEDNING AS?

LUKRA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LUKRA VEILEDNING AS?

LUKRA VEILEDNING AS had revenue of NOK 905,000 in 2024.

Who is the general manager of LUKRA VEILEDNING AS?

Linda Pettersen Myhre is registered as general manager of LUKRA VEILEDNING AS.

Where is LUKRA VEILEDNING AS based?

LUKRA VEILEDNING AS has its business address in Askim.

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.