BIZTRAC BETA
Accounting and bookkeeping

KULERAMMA REGNSKAP AS

Org. no. 916657161 Limited company (AS) Eidsvoll Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 74,000
Equity NOK 643,000
Incorporated 2016
Share capital NOK 30,000

KULERAMMA REGNSKAP AS is registered as a limited company in Eidsvoll, Akershus with organisation number 916657161. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av tjenester innen økonomi og regnskap, samt dertil tilhørende virksomhet, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 74,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 74,000
Equity
NOK 643,000
Est. value
NOK 768,000

Financial health · 2025

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

Who owns KULERAMMA REGNSKAP AS?

INGER-LENE FAGERTUN NANNESTAD
KULERAMMA REGNSKAP AS
NOK 1.5m rev. · NOK 74,000 profit

KULERAMMA REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KULERAMMA REGNSKAP AS

Who owns KULERAMMA REGNSKAP AS?

INGER-LENE FAGERTUN NANNESTAD is the largest registered owner, with 100.0%.

What is the revenue of KULERAMMA REGNSKAP AS?

KULERAMMA REGNSKAP AS had revenue of NOK 1.5m in 2025.

Who is the general manager of KULERAMMA REGNSKAP AS?

Inger-Lene Fagertun Nannestad is registered as general manager of KULERAMMA REGNSKAP AS.

Where is KULERAMMA REGNSKAP AS based?

KULERAMMA REGNSKAP AS has its business address in Råholt.

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.