BIZTRAC BETA
Manufacture of other products of wood and articles of cork, straw and plaiting materials

K. MYKLEBUST AS

Org. no. 996686752 Limited company (AS) Aukra Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 13,000
Equity NOK 361,000
Incorporated 2011
Share capital NOK 100,000

K. MYKLEBUST AS is registered as a limited company in Aukra, Møre og Romsdal with organisation number 996686752. The business is classified under manufacture of other products of wood and articles of cork, straw and plaiting materials (NACE 16.280). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av butikk med rammer, foto og liknende, samt investering i aksjer og andeler, i fast eiendom, samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 13,000
Equity
NOK 361,000
Est. value
NOK 231,000

Financial health · 2025

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

Who owns K. MYKLEBUST AS?

KRISTIAN ANDERS MYKLEBUST
K. MYKLEBUST AS
NOK 1.4m rev. · NOK 13,000 profit

K. MYKLEBUST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K. MYKLEBUST AS

Who owns K. MYKLEBUST AS?

KRISTIAN ANDERS MYKLEBUST is the largest registered owner, with 100.0%.

What is the revenue of K. MYKLEBUST AS?

K. MYKLEBUST AS had revenue of NOK 1.4m in 2025.

Who is the general manager of K. MYKLEBUST AS?

Kristian Anders Myklebust is registered as general manager of K. MYKLEBUST AS.

Where is K. MYKLEBUST AS based?

K. MYKLEBUST AS has its business address in Molde.

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.